You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ivan Andika (Jira)" <ji...@apache.org> on 2025/03/06 05:08:00 UTC
[jira] [Updated] (HDDS-12488) S3G should not append checksum trailer specified by x-amz-trailer
[ https://issues.apache.org/jira/browse/HDDS-12488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Andika updated HDDS-12488:
-------------------------------
Summary: S3G should not append checksum trailer specified by x-amz-trailer (was: Handle x-amz-trailer in S3G)
> S3G should not append checksum trailer specified by x-amz-trailer
> -----------------------------------------------------------------
>
> Key: HDDS-12488
> URL: https://issues.apache.org/jira/browse/HDDS-12488
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> We found that since 1.36.0 introduced a breaking change to their default integrity by using "x-amz-trailer" by default. This will make S3 PutObject and UploadPart requests to add a checksum trailer in the request body (e.g. "x-amz-checksum-crc32:ZS91yQ=="). Our S3G has not handled this so the checksum trailer will be appended in the request body, which is not expected.
> We need to handle this such that if "x-amz-trailer" is detected, we should not include x-amz-checksum-crc32" at the end.
> Resources:
> * https://github.com/boto/boto3/issues/4396
> * https://github.com/boto/boto3/issues/4392
> * https://aws.amazon.com/blogs/aws/introducing-default-data-integrity-protections-for-new-objects-in-amazon-s3/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org