support if-match/if-none-match with s3 uploads #16551
Merged
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.
Description
support if-match/if-none-match with s3 uploads
Motivation and Context
This PR supports optimistic concurrency via
if-match, if-none-match HTTP headers with s3
uploads.
A client that is performing an upload can send
the original ETag together with a conditional header
to ensure that an update will only occur if a certain
the condition has been met. For example, if the If-Match
the header is specified, MinIO verifies that the value
of the ETag specified in the update request is the
same as the ETag for the object being uploaded.
How to test this PR?
This is an extension, requires custom code
to test this.
Types of changes
Checklist:
commit-idorPR #here)