Pascal
join:2003-11-16
Streamwood, IL Reviews:
 ·Comcast
| Their "technology" has another limitation too In order for their "technology" (using the term very loosely here) to work they have to have the source for the web page you are viewing. Unfortunately they did not bother coding in support for compression, so they just corrupt the header from your browser. WOW users goto »www.ericgiguere.com/tools/http-h···wer.html and look for a header named "aaaaaaaaaaaaaaa" with a value of "+++++++++++++". This is what is left of your "accept-encoding" header. It would normally have a value of "gzip,deflate" and is what tells a web server to send you a compressed copy of a webpage. HTML is highly redundant and can compress to less than 10% of its original size. »www.whatsmyip.org/mod_gzip_test/···LmNvbQ== shows you an example and tells you specifically whether or not your browser's request for a compressed page is making it through. |
|
 imrfPremium
join:2002-06-06
Utica, MI | said by Pascal: It would normally have a value of "gzip,deflate" That's what mine shows, and I have WOW. |
|
| Ditto to imrf. Mine says gzip,deflate and I have WoW. |
|
|
|
Pascal
join:2003-11-16
Streamwood, IL Reviews:
·Comcast
| Oops, my mistake. I tested multiple web browsers on multiple PCs and thought I had eliminated everything but the ISP, but turns out McAfee Privacy Service is the "technology" whose authors didn't bother coding in support for compression. As soon as I disable it the headers go out fine. A Google search also confirms this. My apologies. |
|
