Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Do not set
Content-MD5
in S3. (#5226)
[SC-52300](https://app.shortcut.com/tiledb-inc/story/52300/do-not-set-content-md5-in-s3) This PR removes setting the `Content-MD5` header on S3 uploads. There are multiple reasons for this: * The header is [not supported on directory buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-differences.html#s3-express-differences-unsupported-features) used by S3 Express One Zone. * Computing the MD5 hash of the data immediately before uploading them has a performance overhead and does not provide additional security. * We don't do a similar thing in the other cloud VFSes. Validated by: * Creating, writing, consolidating and vacuuming an array on a directory bucket. * Running `quickstart_dense_cpp` on a Google Cloud Storage bucket using the S3 compatibility API. --- TYPE: BUG DESC: Fix incompatibilities with S3 Express One Zone, by stopping setting `Content-MD5` on all S3 uploads. Co-authored-by: KiterLuc <[email protected]>
- Loading branch information