Home/ Questions/Q 7654877
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T12:22:08+00:00

In the APP Engine API, it is mentioned that, if the request comes with

  • 0

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…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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?

    • 0