Commit 5b92634
Do not set
[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]>Content-MD5 in S3. (#5226)1 parent ca51aa0 commit 5b92634
1 file changed
+0
-18
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1786 | 1786 | | |
1787 | 1787 | | |
1788 | 1788 | | |
1789 | | - | |
1790 | | - | |
1791 | | - | |
1792 | | - | |
1793 | | - | |
1794 | | - | |
1795 | 1789 | | |
1796 | 1790 | | |
1797 | 1791 | | |
| |||
1815 | 1809 | | |
1816 | 1810 | | |
1817 | 1811 | | |
1818 | | - | |
1819 | | - | |
1820 | | - | |
1821 | | - | |
1822 | | - | |
1823 | | - | |
1824 | | - | |
1825 | | - | |
1826 | | - | |
1827 | | - | |
1828 | 1812 | | |
1829 | 1813 | | |
1830 | 1814 | | |
| |||
1974 | 1958 | | |
1975 | 1959 | | |
1976 | 1960 | | |
1977 | | - | |
1978 | | - | |
1979 | 1961 | | |
1980 | 1962 | | |
1981 | 1963 | | |
| |||
0 commit comments