[
https://issues.apache.org/jira/browse/HDDS-12488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-12488:
-------------------------------
Target Version/s: 2.0.0, 1.4.2 (was: 1.4.2, 2.0.1)
> S3G should handle the signature calculation with trailers
> ---------------------------------------------------------
>
> 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
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Attachments: image-2025-03-07-09-42-02-201.png
>
>
> From AWS Java SDK V2 2.30.0, The SDK automatically uses the {{CRC32}}
> algorithm to calculate the checksum and provides it in the request. This will
> make default S3 PutObject and UploadPart requests to add a checksum trailer
> in the request body (e.g. "x-amz-checksum-crc32:ZS91yQ==").
> !image-2025-03-07-09-42-02-201.png|width=1509,height=183!
> Starting from 1.36.0, Boto3 upgraded to this new behavior as a way to be
> compatible to the AWS S3 default behavior.
> 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.
> These are the affected versions
> * AWS CLI Version 2: 2.23.0 or later
> * AWS Java SDK V2: 2.30.0 or later
> ([https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/s3-checksums.html])
> * AWS Python SDK (Boto3): 1.36.0 or later
> ([https://github.com/boto/boto3/issues/4392])
> * AWS Go SDK V2: 1.74.1 or later
> ([https://docs.aws.amazon.com/sdk-for-go/v2/developer-guide/s3-checksums.html])
> Other Resources:
> *
> [https://aws.amazon.com/blogs/aws/introducing-default-data-integrity-protections-for-new-objects-in-amazon-s3/]
> *
> [https://docs.aws.amazon.com/sdkref/latest/guide/feature-dataintegrity.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
