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.
Description of changes:
Adds default checksum calculation, deprecates the
AddContentMD5
config option as S3 plans to deprecate MD5 checksums soon, adds two S3 client config options:request_checksum_calculation
andresponse_checksum_validation
with acceptable values for both being eitherwhen_supported
orwhen_required
.request_checksum_calculation
will default towhen_supported
, which means if an operation supports checksum calculation (indicated via modeling), the SDK will calculate the checksum and add the appropriate header. If it is set towhen_required
, the SDK will only compute and send a checksum when the operation requires anhttpRequestChecksum
.response_checksum_validation
also defaults towhen_supported
, which means if an operation models response algorithms, an attempt to validate a response checksum will be made.when_required
will only validate response checksums when response checksum are modeled ANDChecksumMode
is set toenabled
on the command.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.