Closed
Conversation
Member
|
Closing this. As the changes related to this are merged and released. |
|
@prakashsvmx This has never been landed to master? Because it does not work in the current release at all. Always getting S3 errors as all X-Amz-Server-Side-Encryption-* keys are set in query instead of headers. |
|
@mtsyganov Did you ever try if (f)getObject works with encrypted files? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Currently it is possible to put objects to minio with server side encryption by using metaData. Unfortunately it is not possible to get those server side encrypted objects back from minio.
This PR solves the problem by adding to the getObject functions the metaData parameter.