-
-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support upload to S3 buckets with Object Lock enabled #15557
Comments
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 |
Reference Using Content-MD5 when uploading objects 1 Footnotes |
Looks like instead we can use one of
|
Add x-amz-checksum-sha256 request header
Fix does not apply for multipart uploads. |
We previously came to the conclusion in f7977d0 that the |
…art requests with Object Lock parameters" error. Added "Content-MD5" header as x-amz-checksum-sha256 causes "Checksum Type mismatch occurred, expected checksum Type: null, actual checksum Type: sha256." for parts. Fix #15557.
…art requests with Object Lock parameters" error. Added "Content-MD5" header as x-amz-checksum-sha256 causes "Checksum Type mismatch occurred, expected checksum Type: null, actual checksum Type: sha256." for parts. Fix #15557.
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
The text was updated successfully, but these errors were encountered: