Accept-Encoding headers sent by the browser but not received by the server

I have been trying to debug this for several weeks. All browsers of all clients on my home network send "Accept-Encoding: gzip, deflate". However, this header is somehow deleted somewhere before the request goes to the web server. For example, http://www.whatsmyip.org/http_compression/ says: "No, your browser does not request compressed content."

I used Fiddler to make sure all my browsers do send the header. I changed my router. I disabled all antivirus software.

Brighthouse / Roadrunner (local cable provider) says that they do not perform any filtering (and I don’t understand why they are in this case).

Any suggestions would be greatly appreciated!

+6
source share
3 answers

Try using HTTPS.

If you browse the site via HTTPS, nothing between your browser and the web server can change any aspect of the request or response at the HTTP level, including the inclusion of compression, without directly and clearly understanding this fact (check the site certificate in the address bar of the browser and see really whether he).

+2
source share

I had a problem with Accept-Xncoding, and I decided that CA Internet Security Suite was the cause. By disabling wan't enought, you had to delete and then clear the IE cache.

+1
source share

Check your antivirus software. It probably intercepts your outgoing traffic and changes the headers on the fly to get uncompressed content. Lazy programmers do not like to include decompression methods themselves or deal with encoded coding.

Norton Internet Security will overwrite the accepted encoding with this line:

---------------: ----- -------

McAfee rewrites this:

X-McProxyFilter: *************

what I have not yet defined overwrites the following:

Accept-Xncoding: gzip, deflate

You are probably in the same boat. I read Zone Alarm completely destroys the encoding header (which means recalculating the packet size, but why should they care about how much load they put into your system?). If you use Zone Alarm, turn off the "online privacy setting" or something else, and try again.

Every time I saw this problem, it was the result of a crappy antivirus. Completely disabling the ability to receive compressed content without notifying them is dirty.

0
source share

All Articles