Actions
Bug #63951
openrgw: implement S3 additional checksums
% Done:
0%
Source:
Tags:
reef, squid
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Description
Since ~2022, AWS SDKs can be requested to send an additional content checksum, using one of CRC32, CRC32c, SHA1, or SHA256-format digests.
The new content checksums are sent as the value of one of the new content checksum headers, x-amz-checksum-{crc32, crc32c, sha1, sha25 6}.
Depending on the SDK and encoding choices, the checksum header may be sent as a traditional header or aws-chunked trailing header.
Content checksums are stored with S3 objects and can be recovered via S3 metadata requests (e.g., HeadObject, GetObjectAttributes).
Updated by Matt Benjamin 4 months ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 55076
Updated by Matt Benjamin 4 months ago
- Subject changed from rgw: S3 additional checksums are not stored or verified to rgw: implement S3 additional checksums
Updated by Casey Bodley 3 months ago
- Related to Bug #63153: Uploads by AWS Go SDK v2 fail with XAmzContentSHA256Mismatch when Checksum is requested added
Actions