Windows 8 apparently removes content-encoding header from compressed HTTP responses

Question

I\'m not completely sure whether this belongs on SO, but I don\'t know where else to ask.

While I was checking the loading speed of a web app of mine I noticed that

Answer 1

It turned out that the culprit was my antivirus software, Avast, more specifically the integrated real-time network-shield. Turning it off causes responses to appear compressed in the browsers again.

What remains interesting is that Avast was running on the Windows 7 machines as well, even though on those machines responses where compressed where applicable during my tests.