-
Notifications
You must be signed in to change notification settings - Fork 870
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 on PutObjectLockConfigurationRequest #5848
Comments
Hi @Se7enShawn, Thank you for reporting the issue. In AWS SDK for Java From the logs, I see you are connecting to a third-party S3-compatible storage ( Did you get a chance to try the temporary workaround mentioned in the shared announcement? You can disable the new behavior with the You should check with the third-party storage provider regarding the support for the changes introduced on Let me know if you see any concerns regarding this change when using the AWS S3 directly. Regards, |
Thank you,
Content-MD5 is not generated on PutObjectLockConfigurationRequest:
|
Hello @Se7enShawn,
Could you please help understand, the usage for this header in your requests? Is there specific validation in your application that depends on this header? Or you experiencing any specific error when connecting to your third-party S3 like service due to the missing Regards, |
It is the third-party S3 server that currently requires the Content-MD5 header on the PutObjectLockConfigurationRequest call. I have reported this difference to them, and I hope they will update their system. In the meantime, is there a way to force the creation of the Content-MD5 header for this call when using an S3AsyncClient CRT-based? |
Describe the bug
From 2.30 version calling PutObjectLockConfigurationRequest Content-MD5 header is no longer generated
Regression Issue
Expected Behavior
This is the log with 2.29.x:
Sending Request: DefaultSdkHttpFullRequest(httpMethod=PUT, protocol=https, host=****-**.******.it, encodedPath=/202513116343bucket, headers=[amz-sdk-invocation-id, Content-Length, Content-MD5, Content-Type, User-Agent], queryParameters=[object-lock])
Current Behavior
This is the log with 2.30.x:
Sending Request: DefaultSdkHttpFullRequest(httpMethod=PUT, protocol=https, host=****-**.******.it, encodedPath=/202513116104bucket, headers=[amz-sdk-invocation-id, Content-Length, Content-Type, User-Agent], queryParameters=[object-lock])
Reproduction Steps
Possible Solution
Generate the Content-MD5 for the request
Additional Information/Context
No response
AWS Java SDK version used
2.30.10
JDK version used
17
Operating System and version
Windows 11 and Unix
The text was updated successfully, but these errors were encountered: