fix: disable S3 flexible checksums for s3proxy compatibility#3747
Open
vedranjukic wants to merge 1 commit intomainfrom
Open
fix: disable S3 flexible checksums for s3proxy compatibility#3747vedranjukic wants to merge 1 commit intomainfrom
vedranjukic wants to merge 1 commit intomainfrom
Conversation
brunogrbavac
previously approved these changes
Feb 13, 2026
Signed-off-by: Vedran Jukic <vedran.jukic@gmail.com>
vedranjukic
force-pushed
the
checksums-s3proxy-compatibility
branch
from
10d3c2f to
f167bab
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Disable AWS SDK v3 flexible checksums to fix compatibility with s3proxy (S3 compatibility layer for Azure Blob Storage).
AWS SDK v3's
@aws-sdk/middleware-flexible-checksumssendsx-amz-checksum-algorithmand related headers by default on every request. s3proxy does not implement these headers, causing requests to fail when using Azure Blob Storage as the backend.Documentation
Notes
This is safe because Azure Blob Storage has its own built-in integrity checks, making the S3 flexible checksums redundant.
WHEN_REQUIREDensures checksums are only sent when S3 explicitly mandates them (which s3proxy never will).No documentation changes needed — this is an internal configuration fix with no user-facing API changes.
mount-s3binary supports--upload-checksums off(alternatives:crc32cwhich is the default)requestChecksumCalculation/responseChecksumValidationoptions accept'WHEN_REQUIRED'or'WHEN_SUPPORTED'— we use'WHEN_REQUIRED'to minimize unnecessary headers