Skip to content
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

Missing Content-MD5 http header for put request on object with bucket defined Lock #1177

Open
r0ro opened this issue Mar 24, 2021 · 2 comments · May be fixed by #1353
Open

Missing Content-MD5 http header for put request on object with bucket defined Lock #1177

r0ro opened this issue Mar 24, 2021 · 2 comments · May be fixed by #1353

Comments

@r0ro
Copy link

r0ro commented Mar 24, 2021

When an aws s3 bucket is configured with Object Lock in order to benefit from WORM feature the upload
cf: https://aws.amazon.com/fr/blogs/storage/protecting-data-with-amazon-s3-object-lock/

the upload fails with the following error:

Content-MD5 HTTP header is required for Put Object requests with Object Lock parameters

Is there a way add Content-MD5 header to the request ?

I could have used --add-header=NAME:VALUE but since I'm using built in gpg encryption, I can't compute the md5 before running the command.

Any idea ?

@eullerborges eullerborges linked a pull request Nov 13, 2023 that will close this issue
@eullerborges
Copy link

A bit late here, but I managed to get this working. I'm not familiar with the code base and don't really know if there are implications, but please take a look at #1353.

@rampageservices
Copy link

A bit late here, but I managed to get this working. I'm not familiar with the code base and don't really know if there are implications, but please take a look at #1353.

Looks great. I added a PR review. Do you want to share your efforts for MD5 in a gist or elsewhere and let me know where you got stuck?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants