Nope... I have that feature. It's what screws everything up.
Most AV software strips or mangles the Accept-Encoding HTTP header so that no matter how your browser is requesting the page and how the server is serving it, you will never get the gzipped version.
If the web dev is really savvy, she can use the Google technique
* if there is no cookie, set one saying there is no gzip
* force delivery of a gzipped javascript file that, if interpreted correctly, sets a cookie saying the browser can accept gzipped content. If it truly doesn't, then nothing happens
* if the client has the right cookie, send gzipped content no matter what the Accept-Encoding header says.
[
stevesouders.com...]
Of course, .000001% of websites are doing this. So b/c I'm running AV software, I'm not getting gzipped content.
Not a problem on a high-speed connection, but when I'm on my high-latency satellite connection, it would speed things up a fair bit.
Of course, what would be really handy would be if the HTTP spec allowed me to *send* gzipped content for all post headers/data. Since the upload speed is the real bottleneck, that's the killer.