aws/signer/v4: Fix signer to not double sign Content-Length header #1743
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
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.
Fixes the SDK's AWS SigV4 signer to not double sign the
content-lengthheader. If theContent-Lengthheader was manually set on the http.Request, that value would be included along with the Request.ContentLength value as a common separated list when computing the string to sign.This fix updates the signer to always ignore the
content-lengthheader, and only use theRequest.ContentLengthparameter. This change also matches http.Request's behavior of ignoring theContent-Lengthheader if set.Fixes #1728
Replaces: #1729