Checksum support on multipart upload S3 compatibility?
Hi Tigris team - does Tigris support the x-amz-checksum methods to validate the uploaded content? I just tried this with CreateMultipartUpload / UploadPart / CompleteMultipartUpload and it seems like the headers are accepted and pushed through, but the data is not rejected with 400 BadDigest if the checksum is mismatched. A regular PutObject with a mismatched Content-MD5 header does return 400 BadDigest, but not with a mismatched crc32.
Is there any way to do checksums on multipart uploads?
Solution
Thanks for flagging this, I do see your point about the current behavior with flexible checksums misleading. Let me relay your message to the team. We are not treating those headers as enforced integrity checks on multipart uploads today and responses may still echo them.