Updates:
Status: Fixed
Comment #9 on issue 8916 by j...@chromium.org: content encoding problem
behind company proxies
http://code.google.com/p/chromium/issues/detail?id=8916
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or C
Comment #8 on issue 8916 by marco.barentsz: content encoding problem behind
company proxies
http://code.google.com/p/chromium/issues/detail?id=8916
After doing a little research I can confirm our company is using BlueCoat
ProxySG
appliances and is stripping content - ie most ActiveX content.
Comment #7 on issue 8916 by bugdro...@chromium.org: content encoding
problem behind company proxies
http://code.google.com/p/chromium/issues/detail?id=8916
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=12784
---
Updates:
Status: Assigned
Owner: j...@chromium.org
Comment #6 on issue 8916 by j...@chromium.org: content encoding problem
behind company proxies
http://code.google.com/p/chromium/issues/detail?id=8916
I have a pending CL that checks the status code of the page when content
t
Comment #5 on issue 8916 by j...@chromium.org: 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
Comment #4 on issue 8916 by j...@chromium.org: 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.
Comment #3 on issue 8916 by j...@chromium.org: content encoding problem
behind company proxies
http://code.google.com/p/chromium/issues/detail?id=8916
I believe there was a typo in that last comment. The command line option
should have
two leading hyphens, not one, and hence should look lik
Comment #2 on issue 8916 by j...@chromium.org: 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
Updates:
Cc: j...@chromium.org j...@chromium.org anan...@chromium.org
js...@chromium.org
Comment #1 on issue 8916 by xly...@chromium.org: content encoding problem
behind company proxies
http://code.google.com/p/chromium/issues/detail?id=8916
(No comment was entered for this change.)
Status: Unconfirmed
Owner:
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 8916 by marco.barentsz: content encoding problem behind company
proxies
http://code.google.com/p/chromium/issues/detail?id=8916
Chrome Version :
URLs (if applicable) :
Other browsers tested:
Add OK or F
10 matches
Mail list logo
