mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-27 06:35:54 +03:00
[GH-ISSUE #791] Avoid setting "X-Goog-Hash" header in downloads when range is provided #129
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#129
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mcrichton on GitHub (May 20, 2022).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/791
Expected: the "X-Goog-Hash" is not set for ranged download requests (I cannot find any documentation saying this should be the case, but doing a range GET request against a blob in "real" GCS does not return an "X-Goog-Hash" header)
Actual: the "X-Goog-Hash" is set regardless of whether or not a ranged request is being made
This notably causes issues when using
fake-gcs-serverwith the Google Cloud Python SDK, as the SDK finds an MD5 mismatch (sincefake-gcs-server(correctly, according to Google's own docs 😔) returns the MD5 for the entire blob) and crashes@dnerdy commented on GitHub (Jun 1, 2022):
I just sent a range request to GCS, and it looks like x-goog-hash is always included.
This request:
Outputs:
And this request:
Returns:
@mcrichton commented on GitHub (Jun 2, 2022):
A mistake on my end, on re-checking. Thanks for verifying!