Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Amazon’s S3 Management Console, I’m trying to add metadata, with the key being “Vary” and the value being “Accept-Encoding”.
This seems to work, I hit save. But when I hit refresh it disappears, as if Amazon rejected the tag. The file in question is a gzip compressed javascript file.
My other headers are working and added properly (Content-Type, Cache-Control, etc.). I’ve tried adding the vary header with only a Content-Type header too and it fails in the same way.
Given that S3 is going to serve up the exact same static blob no matter what, it doesn’t really make sense to serve a
Varyheader, which tells the browser that the resource representation will vary depending on the request’s content negotiation headers.S3 doesn’t do that, so it doesn’t surprise me that they won’t allow
Varyheaders to be set on an object.