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

Content-Encoding: aws-chunked should not be stored #2218

Open
akheron opened this issue Jan 27, 2025 · 0 comments
Open

Content-Encoding: aws-chunked should not be stored #2218

akheron opened this issue Jan 27, 2025 · 0 comments

Comments

@akheron
Copy link

akheron commented Jan 27, 2025

After upgrading AWS SDK for Java from v2.29.1 to v2.30.6, I noticed that S3Mock started returning Content-Encoding: aws-chunked response header when reading objects through the presigned url mechanism. It seems that the new version of the SDK adds Content-Encoding: aws-chunked with PutObject requests, and S3Mock stores the content encoding header value with the object.

However, according to AWS docs, the aws-chunked value should be stripped before storing the header value:

Amazon S3 stores the resulting object without the aws-chunked value in the content-encoding header. If aws-chunked is the only value that you pass in the content-encoding header, S3 considers the content-encoding header empty and does not return this header when your retrieve the object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant