You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 addsContent-Encoding: aws-chunked
withPutObject
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:The text was updated successfully, but these errors were encountered: