Status: Untriaged
Owner: [email protected]
CC: [email protected]
Labels: Pri-2 OS-All Area-Misc Size-Medium

New issue 14801 by [email protected]: bzip2 encoded results may be  
corrupted by proxies (such as Vodaphone (UK) Mobile Broadband)
http://code.google.com/p/chromium/issues/detail?id=14801

What steps will reproduce the problem?
1.Use a proxy with an ISP such as Vodaphone (UK) Mobile Broadband
2.Visit a page that is bzip2 encoded, such as
http://ukcp09.defra.gov.uk/content/view/16/6/index.html
3. Page will be corrupted.

What is the expected output? What do you see instead?

Garbled characters.

To repro, use another ISP, and visit the above URL:
http://ukcp09.defra.gov.uk/content/view/16/6/index.html
Then modify the URL to read:
view-cache:http://ukcp09.defra.gov.uk/content/view/16/6/index.html
You should see it was bzip2 encoded.

Repeat the process using a problematic proxy.
You'll (incorrectly) see a content encoding of gzip.
Extract the gzip decoded file.  Run bzip2 on it, and it should decompress
porperly.

The above bug was deduced from reports in the following forum thread:
http://www.google.com/support/forum/p/Chrome/thread?
tid=24436bd4ef660e1e&hl=en

Possible remedition: Terminate support for bzip2. ...or convince Vodaphone
to stop trashing content... or find a way to tell Vodaphone and others like
it to not damage content.  Perhaps there is a way (for example) to to have
serving sites add an HTTP header when serving bzip2:

Warning: 214 msgwsl11 "Transformation applied"

and that would discourage Vodaphone. Alternatively, perhaps the above
warning header can be detected by chrome, and then bzip can be
discontinued.

--
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to