Comment #4 on issue 8916 by [email protected]: content encoding problem behind company proxies http://code.google.com/p/chromium/issues/detail?id=8916
Researching the error message: Content Transformation Error on the web, I'm suspicious that you may be using a proxy filter from BlueCoat. I'm guessing that the "content transformation" that is being attempted is that they are trying to do something like strip active content. Since they can't decipher this encoding (they haven't put in support for SDCH), they simply provide the error page :-(. IMO, it would have been *much* nicer if the proxy product modified the "accept- encoding" header in the outbound GET request to not support SDCH, rather than block the response when the content is indeed encoded :-/. Several AV products seem to take such a tack. As a result, this is in some sense a bug in your proxy. Reading on the web, you *can* probably configure (at least the proxy from BlueCoat) to exclude some domains from certain filter transformations, and that would be the nicest work-around. As I said, it would be nicer of the proxy was more graceful in its handling of content requests, but I see no rapid way of getting this plausible proxy bug fixed rapidly. That said, SDCH needs to function correctly in the presence of all sorts of proxies. I'm trying to figure out how we can detect this content corruption, and respond gracefully. There is a *chance* that the proxy provides some error status with the interstitial error page it generates. As a result, I *might* be able to detect this status code, disable SDCH, and transparently re-issue the GET. I'll work on a patch to try to do that. Are you building your own Chromium to experiment with, or are you depending on a dev or beta channel release to test with? -- 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 -~----------~----~----~----~------~----~------~--~---
