Comment #5 on issue 8916 by [email protected]: content encoding problem behind company proxies http://code.google.com/p/chromium/issues/detail?id=8916
A coworker (Bryan McQuade) found the following very helpful information, and based on his findings, I'll try to code up a patch to gracefully handle this situation (non- 200 status code). Hopefully it can be done in the dev build by next week (tiny chance it will get into the next beta build as well). From the BlueCoat Version SGOS 4.2.1 manual: "The ProxySG issues a transformation_error exception (HTTP response code 403), when the server sends an unknown encoding and the ProxySG is configured to do content transformation." "The ProxySG issues an unsupported_encoding exception (HTTP response code 415 - Unsupported Media Type) when the ProxySG is unable to deliver content due to configured policy." Bryan went on to agree that we should treat all 4xx response codes as an indicator that sdch should be disabled for that client (this should go into the sdch whitepaper as well): 4xx: Client Error - The request contains bad syntax or cannot be fulfilled http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1.1 There is a Cache-Control: no-transform feature that is supposed to tell proxies not to modify the response, but BlueCoat does not honor it by default. Again, quoting from the BlueCoat manual: "The HTTP proxy ignores Cache-Control: no-transform directive of the OCS. To change this, write policy to disallow compression or decompression if Cache-Control: no-transform response header is present." The manual also states: "The ProxySG treats multiple content encoding (gzip, deflate or gzip, gzip) as an unknown encoding. (These strings indicate the content has been compressed twice.)" Since SDCH is almost always supplied as "content-encoding=gzip,sdch" the current default config for this ProxSG will always corrupt SDCH encoding :-(. -- 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 -~----------~----~----~----~------~----~------~--~---
