trueleo commented on issue #3725: URL: https://github.com/apache/arrow-rs/issues/3725#issuecomment-1436624552
I was considering how to go about fixing this. The main objective is to make the request work with object locking, so I tried sending the `x-amz-checksum-sha256` header, and it worked. For `x-amz-checksum-sha256`, the hash digest is encoded with `base64`. This can be quickly added, but internally, it seems that the `object_store` already calculates the sha256 digest for the request body (which is later set as `x-amz-content-sha256` and encoded using `hex-encode`). I have two things in mind: * Should Content-MD5 be added as an option just for the sake of support, or should `x-amz-checksum-` be favored ? reference: https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html * If so, can the same digest be used for `x-amz-content-sha256` and `x-amz-checksum-sha256`? ( Still testing this out for multipart upload ) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
