You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add config and change default behavior of checksum middleware
* regenerate client
* regenerate clients
* merge protocol test code from main
* merge from main
* add more test cases
* add changelog
* modify s3 internal test
* separate checksum config check and workflow
* restore s3 test
* remove unused md5 header
* separate checksum config and workflow
* change default checksum to const
* add checksum unset enum and modify comment of cfg
* change comment
* Update aws/checksum.go
* change checksum value check logic
* remove old check
* correct unseekable stream logic without tls and its test cases
* revert extra codegen
* change tmv1 upload test cases after introducing flex checksum
* add error test case for crc64
* change test name
* default tmv1 checksum and add flex checksum metrics tracking
* regenerate client and add metrics mw test
* add comment to exported type
* update s3 snapshot
* update tmv1 integ test
* exclude default checksum from presign op
* reorder feature id and simplify metric tracking test
* update changelog
---------
Co-authored-by: Tianyi Wang <[email protected]>
Co-authored-by: Luc Talatinian <[email protected]>
"description": "S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The checksum algorithm used by default now becomes CRC32. Checksum behavior can be configured using `when_supported` and `when_required` options - in code using RequestChecksumCalculation, in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION. The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using `when_supported` and `when_required` options - in code using ResponseChecksumValidation, in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.",
Copy file name to clipboardExpand all lines: codegen/smithy-aws-go-codegen/src/main/java/software/amazon/smithy/aws/go/codegen/AwsHttpChecksumGenerator.java
Copy file name to clipboardExpand all lines: codegen/smithy-aws-go-codegen/src/main/java/software/amazon/smithy/aws/go/codegen/AwsHttpPresignURLClientGenerator.java
0 commit comments