additional fixes for copyobject to handle sse-c encrypted #6
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.
replication
Description
Motivation and Context
Fix replication of metadata updates via CopyObject API on SSE-C encrypted objects
avoid infinite proxying on SSE-C encrypted objects
How to test this PR?
run
mc replicate resync
on already replicated content - will not log error on sourceupdate tags on sse-c encrypted object - should replicate with this fix
mc cp
with sse-c can lead to 429 Too many requests from infinite proxying because object options did not set opts.ProxyRequest for sse-c properly.Types of changes
Checklist:
commit-id
orPR #
here)