About header: Accept-Encoding: gzip,deflate
Most clients today send the following header when making a request:
Accept-Encoding: gzip,deflate
This means that the client will accept content that is compressed and will decompress it (on the client side).
I have uploaded a compressed html page (gzip compression) and added the header " Content-Encoding: gzip " in the response. When I request this page with a browser, S3 sends the compressed page with the header indicating that the response is compressded. As expected it works. The page is successully rendered.
So far, so good. Then I wondered what would happen if the client did not support compressed content? What if the client did not sent " Accept-Encoding: gzip,deflate "?
I did the test and S3 sends exactly the same compressed response. Therefore the client could not render the page.
I would have hoped that S3 would have noticed that the response is gzip and would have decompressed it (and removed the Content-Encoding header).
Dear Amazon, could you imprement this feature please?
It would help me a lot. You already do https so decompressing a few responses should not be too much for you I hope.
Accept-Encoding: gzip,deflate
This means that the client will accept content that is compressed and will decompress it (on the client side).
I have uploaded a compressed html page (gzip compression) and added the header " Content-Encoding: gzip " in the response. When I request this page with a browser, S3 sends the compressed page with the header indicating that the response is compressded. As expected it works. The page is successully rendered.
So far, so good. Then I wondered what would happen if the client did not support compressed content? What if the client did not sent " Accept-Encoding: gzip,deflate "?
I did the test and S3 sends exactly the same compressed response. Therefore the client could not render the page.
I would have hoped that S3 would have noticed that the response is gzip and would have decompressed it (and removed the Content-Encoding header).
Dear Amazon, could you imprement this feature please?
It would help me a lot. You already do https so decompressing a few responses should not be too much for you I hope.
You must be logged in to post a comment.