fix(object_store): Include Content-MD5 header for S3 DeleteObjects #5415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
S3 API specification requires the presence of this header for all
DeleteObjects
requests to general purpose buckets:Some platforms, such as MinIO, enforce this requirement, rejecting requests that don't include the header.
I have successfully tested the change locally against MinIO.
What changes are included in this PR?
Content-MD5
header unconditionally for allDeleteObjects
requestsNo breaking changes, platforms not interested in the header will ignore it.
Closes #5414