Hello, This is something which I'm able to reproduce occasionally: for static content deployed on google app engine the frontend / edge cache sometimes serves the content gzipped even if the client doesn't ask for it (ie. it doesn't send an "Accept-Encoding" header). My application is deployed in the EU region. This isn't generally a problem since most (all?) browsers send Accept-Encoding: deflate, gzip, however cURL doesn't by default (only if you specify --compressed).
Perhaps the URL was first accessed by a browser supporting gzip, it was cached in the compressed format and is being (erroneously) served this way? Note: even when the response is unexpectedly compressed, it contains the correct "Content-Encoding: gzip" header, but cURL doesn't decompress it. Cheers, Attila -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1df7fc04-b55a-46e3-a8f2-7b81eef96ba2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
