-
Notifications
You must be signed in to change notification settings - Fork 271
Open
Description
The Content-MD5 request header is required for all Multi-Object Delete requests, but using s3proxy 3.0.0 the command fails because x-amz-checksum-crc32 is not supported:
[s3proxy] E 01-21 21:58:25.952 S3Proxy-Jetty-36 o.gaul.s3proxy.S3ProxyHandler:527 |::] Unknown header x-amz-checksum-crc32 with URI /testbucket/
Changing the client configuration to use checksum only when required, did NOT fix the issue, because for the DeleteObjects command, they are always necessary:
.request_checksum_calculation(
aws_sdk_s3::config::RequestChecksumCalculation::WhenRequired,
)
.response_checksum_validation(
aws_sdk_s3::config::ResponseChecksumValidation::WhenRequired,
)A workaround is creating an interceptor that will remove the x-amz-checksum-crc32 header from requests.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels