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
When uploading objects to S3, it's possible to specify a content-encoding attribute which is currently not possible with the operator.writer_with method. The content-encoding attribute is important because compressed files uploaded to a (public) S3 bucket wouldn't correctly decompress on the browser without it.
Suppose a brotli compressed css file is uploaded to S3. Without the content-encoding header, the browser wouldn't know how to decompress it before attempting to use it. The content-type header alone does not make it possible to guess how to decode a compressed file.
I imagine a content_encoding method to the writer_with method of the operator should help:
Feature Description
When uploading objects to S3, it's possible to specify a content-encoding attribute which is currently not possible with the operator.writer_with method. The content-encoding attribute is important because compressed files uploaded to a (public) S3 bucket wouldn't correctly decompress on the browser without it.
Here's what the AWS SDK method looks like: https://docs.rs/aws-sdk-s3/latest/aws_sdk_s3/operation/put_object/builders/struct.PutObjectFluentBuilder.html#method.content_encoding
Problem and Solution
Suppose a brotli compressed css file is uploaded to S3. Without the content-encoding header, the browser wouldn't know how to decompress it before attempting to use it. The content-type header alone does not make it possible to guess how to decode a compressed file.
I imagine a content_encoding method to the writer_with method of the operator should help:
Additional Context
No response
Are you willing to contribute to the development of this feature?
The text was updated successfully, but these errors were encountered: