presigner: Remove content-type header if empty/nil body for streaming operation
#967
Conversation
This file contains 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
54732ce to
2ac0d23
Compare
jasdel
reviewed
Dec 11, 2020
jasdel
approved these changes
Dec 11, 2020
1 task
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Presigner clients should not send content-type header if a streaming operation has an empty or nil payload. This is to reduce burden on customers as they have to sign content-type header.
S3 operations need presigners to generate request with unsigned payload. Previously we were incorrectly only converting presigner to be unsigned for streaming operations. This conversion to unsigned payload request, should apply on each s3 presigned url request .