Skip to content

azurestore: Support servecontent - #1381

Open
quality-leftovers wants to merge 16 commits into
tus:mainfrom
quality-leftovers:azurestore-servecontent
Open

azurestore: Support servecontent#1381
quality-leftovers wants to merge 16 commits into
tus:mainfrom
quality-leftovers:azurestore-servecontent

Conversation

@quality-leftovers

Copy link
Copy Markdown
Contributor

Supersedes #1234

Implement ContentServerDataStore for azure blob storage too, tests with azurite+azure blob are ok.
Incomplete range requests (Range: bytes=100- ) are not supported, hope that's ok

Behavioral changes

  • Return 200 OK instead of 204 NoContent for empty file. This is currently inconsistent between stores. See e2e test TestDownload. I'm unsure on whether this is ok.

xelat09 and others added 16 commits January 12, 2025 21:00
…nses [StatusRequestedRangeNotSatisfiable, StatusPreconditionFailed, StatusNotFound] and support StatusNotModified response for conditional requests. Respond with 200 OK instead of 204 NoContent for empty blob

azurestore: Update ServeContent.

Update ServeContent to support conditional requests, range requests.
Relevant headers, including some azure specific will be passed on to clients.

For empty blobs the response changes from 204 No Content to 200 OK.
This is consistent with `http.ServeFile` and azure blob API behavior. Currently
this is not consistent across all stores, since GCS does not support empty blob and
S3 returns 204 (however S3 API itself should return 200 OK for empty objects).
@quality-leftovers
quality-leftovers marked this pull request as ready for review June 24, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants