fix(s3): respect content encoding for multipart upload initialization#7274
Merged
Xuanwo merged 2 commits intoapache:mainfrom Mar 24, 2026
Merged
Conversation
dosubot
Bot
added
size:XS
koushiro
approved these changes
Mar 24, 2026
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
4 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.
Which issue does this PR close?
Closes #7273
Rationale for this change
content-encoding is a valid request header for multipart upload creation, but it doesn't seem to be respected now.
The issue was found when I used opus-4.6 to do a sanity check to compare the request header difference between plain PUT and multipart upload, seems to be the only left one.
What changes are included in this PR?
Add the header to the request.
Are there any user-facing changes?
No
AI Usage Statement
Opus 4.6 helped me make the change.