Comment #2 on issue 8916 by [email protected]: content encoding problem behind company proxies http://code.google.com/p/chromium/issues/detail?id=8916
The cause of this problem is more than likely the experimental SDCH encoding. As a temporary work-around, you can add the following command line option when starting Chrome: -enable-sdch=nothing If you start Chrome from an icon, you can right click on the icon, and then select "properties." It the dialog that appears, there is probably a "target" box that has somthing like the following: C:\Users\somename\AppData\Local\Google\Chrome\Application\chrome.exe You should add a space after that, and then the command line argument I listed. It will then look something like: C:\Users\jar\AppData\Local\Google\Chrome\Application\chrome.exe -enable-sdch=nothing Please tell me if this temporary work-around takes care of it. I'm discussing the problem, and will try to post a fix on our next beta release and our next dev channel release. Jim FYI, in case you wanted more details: The argument to this command line option is the list of domains that you wish to support sdch. If you give it a list, then *ONLY* those domains are used. In this case, we named a bogus domain called "nothing" and only that domain would have sdch compression advertised. If you're curious as to what SDCH is, google around for "Shared Dictionary Compression over HTTP" -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
