Repository navigation
Support upload to S3 buckets with Object Lock enabled #15557
Description
Activity
This would need to be set conditionally depending on the object lock configuration 1 of the bucket.
Footnotes
This would need to be set conditionally depending on the object lock configuration 1 of the bucket.
Footnotes
It would probably be easier to just set the
Content-MD5unconditionally for al uploads.Reference Using Content-MD5 when uploading objects 1
Footnotes
Looks like instead we can use one of
x-amz-checksum-crc32: ChecksumCRC32 x-amz-checksum-crc32c: ChecksumCRC32C x-amz-checksum-sha1: ChecksumSHA1 x-amz-checksum-sha256: ChecksumSHA256- added a commit that references this issue
on Feb 12, 2024 Fix does not apply for multipart uploads.
- added a commit that references this issue
on Mar 8, 2024 - linked a pull request that will close this issueFix #15557 for multipart uploads #15699
on Mar 8, 2024 - added a commit that references this issue
on Mar 8, 2024 - added a commit that references this issue
on Mar 8, 2024
Is your feature request related to a problem? Please describe.
Currently when trying to upload a file into an S3 bucket which has Object Lock enabled, this error shows:
Describe the solution you'd like
Calculate MD5 hash for the file and upload it in the request header along with the file.
Describe alternatives you've considered
Disabling Object Lock on the S3 bucket temporarily to be able to upload the file.
Additional context
Discussion about workarounds for this issue