-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Append aws-chunked
to Content-Encoding
header if present
#2859
Conversation
Codecov ReportBase: 93.54% // Head: 93.55% // Increases project coverage by
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## develop #2859 +/- ##
========================================
Coverage 93.54% 93.55%
========================================
Files 63 63
Lines 13398 13400 +2
========================================
+ Hits 12533 12536 +3
+ Misses 865 864 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@nateprewitt I'll wait until #2860 is merged, then I'll update the functional test to rely on the defaults in the client constructor. |
8661111
to
6a52ac3
Compare
…parate line in functional test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good once the tests wrap
Primarily in various S3 operations, users may provide a
ContentEncoding
parameter. This tells the service how the content that is being sent/requested is encoded. An example of this would begzip
. However, for streaming AWS operations (i.e. ones that have trailers) where aChecksumAlgorithm
parameter is provided, the SDK is currently overriding any user input toaws-chunked
. Instead this special content encoding should be appended to the user input.