6

In the APP Engine API, it is mentioned that, if the request comes with "Accept-Encoding" set, then it will automatically compress the response.

But when I look at the request, the header is not there. but at the browser, it is set. when I try to explicitly set the header(with JQuery ajax function), there is a message:

 Refused to set unsafe header "Accept-Encoding"

But this situation is not occurring when working in local host - request has the "Accept-Encoding" header. this happens only after publishing. but not allowing to set the "Accept-Encoding" explicitly happens always.

I searched everywhere, but couldn't find a explanation to the problem. It would be really helpful if someone can explain...

mmmmmm
  • 32,227
  • 27
  • 88
  • 117
KTB
  • 1,499
  • 6
  • 27
  • 43

2 Answers2

7

You have two different problems:

  1. App Engine does not compress reply. GAE uses a number of factors to determine if response needs to be compressed. It takes content type and user agent into account when deciding. See the answer by Nick Johnson (from GAE team).

  2. jQuery refuses to set "Accept-Encoding" header. Note that this is a jQuery issue and has nothing to do with GAE. See this: Is it possible to force jQuery to make AJAX calls for URLs with gzip/deflate enabled?

Community
  • 1
  • 1
Peter Knego
  • 79,991
  • 11
  • 123
  • 154
  • 1
    thanks for the reply... but as I said before, the problem I'm having is in the HTTPRequest header, "Accept-Encoding" is null. So as GAE has explained, there is no way the GAE can recognize whether to compress. But as I've explained, when I'm working in localhost, "Accept-Encoding"is not null. So i'm bit confused here. – KTB Mar 20 '12 at 17:29
  • Oddly, when I use localhost, Accept-Encoding is null, even though in IntelliJ it shows up during debug in the httpRequest. But if I use getHeader("Accept-Encoding"), it returns null. Apparently GAE must strip out this header. – Johann Jan 29 '18 at 16:32
3

I have a similar problem as in the HTTPRequest header, "Accept-Encoding" is null. As GAE has explained it looks for Accept-Encoding and User-Agent headers, if it wants to compress. but in my case there is no way the GAE can recognize whether to compress.

From the browser, then header is set, but in the request header, it is not.

BTM
  • 31
  • 1