Remove Transfer-Encoding from streaming signature #638
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
http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html doesn't provide any detail related to `Transfer-Encoding` to be a valid header as a requirement. Additionally also Transfer-Encoding is used as part of signature request incorrectly because the transfer coding names are case insensitive[1] i.e when the canonical request is generated should be generated as lower cased value instead. ``` content-encoding:aws-chunked content-type:image/jpeg host:***REDACTED*** transfer-encoding:Chunked user-agent:aws-sdk-iOS/2.5.2 iOS/10.2 en_US transfer-manager x-amz-acl:public-read x-amz-content-sha256:STREAMING-AWS4-HMAC-SHA256-PAYLOAD x-amz-date:20170413T050829Z x-amz-decoded-content-length:1024000 ``` [1] - http://greenbytes.de/tech/webdav/rfc7230.html#transfer.codings
|
Can this be reviewed ? |
|
Anyone? |
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.
http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html
doesn't provide any detail related to
Transfer-Encodingto be a validheader as a requirement.
Additionally also Transfer-Encoding is used as part of signature
request incorrectly because the transfer coding names are case
insensitive[1] i.e when the canonical request is generated should
be generated as lower cased value instead.
[1] - http://greenbytes.de/tech/webdav/rfc7230.html#transfer.codings