Skip to content
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

Encryption headers only partially stored and returned #1178

Closed
afranken opened this issue Jun 19, 2023 · 0 comments · Fixed by #1190
Closed

Encryption headers only partially stored and returned #1178

afranken opened this issue Jun 19, 2023 · 0 comments · Fixed by #1190
Assignees
Labels

Comments

@afranken
Copy link
Member

APIs like PutObject let customers send headers starting with x-amz-server-side-encryption, APIs like GetObject and HeadObject should return them
From PutObject

x-amz-server-side-encryption: ServerSideEncryption
x-amz-server-side-encryption-customer-algorithm: SSECustomerAlgorithm
x-amz-server-side-encryption-customer-key-MD5: SSECustomerKeyMD5
x-amz-server-side-encryption-aws-kms-key-id: SSEKMSKeyId
x-amz-server-side-encryption-context: SSEKMSEncryptionContext
x-amz-server-side-encryption-bucket-key-enabled: BucketKeyEnabled

Currently, S3Mock only accepts the x-amz-server-side-encryption and x-amz-server-side-encryption-aws-kms-key-id, values are stored and returned.

S3Mock should accept all encryption headers and return them.

@afranken afranken self-assigned this Jun 19, 2023
afranken added a commit that referenced this issue Jun 24, 2023
afranken added a commit that referenced this issue Jun 26, 2023
afranken added a commit that referenced this issue Jun 26, 2023
afranken added a commit that referenced this issue Jun 26, 2023
afranken added a commit that referenced this issue Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant