When trying to understand why Chrome developer tools was showing that content was not "gzip"-ed for my website, I realized that the behaviour was dependent on what the User-Agent string was. If I changed it to a "bogus" user agent, Chrome would show that the content was gziped, if however I used the normal User Agent, the content would be unzipped and shown as transfer-encoding: chunked.
Firstly, is Eset doing decompression of web-pages on the fly and not returning the content to it's original gziped form? And secondly, I'm presuming that the content is unzipped so that Eset can examine the contents for viruses, malware, etc. - does this mean that if I change my User-Agent to something not recognized by the Eset that I won't be protected?
