RFC2616 "Transfer-Encoding: gzip, chunked" not handled properly
Reported by hvrie...@gmail.com, Aug 30 2011
Chrome Version : 12.0.742.112 (Developer Build 90304) OS Version: Ubuntu 11.04 URLs (if applicable) : Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: ? Firefox 4.x: FAIL IE 7/8/9: ? What steps will reproduce the problem? 1. Access text/html document via server which sends entity with "Transfer-Encoding: gzip, chunked" http header (and no "Entity-Encoding" header) What is the expected result? Transparent decompression of `gzip` transfer-coding and properly rendered html page. What happens instead? Raw display of gzipped compressed octet-stream Please provide any additional information below. Attach a screenshot if possible. See also https://bugzilla.mozilla.org/show_bug.cgi?id=68517 for more details about this issue. Opera seems to be the only RFC2616 compliant browser in this regard.
Aug 30 2011,
Sep 16 2011,
Technically, Chrome is in compliance with RFC2616. We don't include a "TE" field, indicating we don't support any transfer-encodings, other than "chunked". It's actually the server that's misbehaving, in your example. There's also a link to a discussion about problems with double-gzipping the "TE" field causes on some servers, near the bottom of your link. Think we're probably better off keeping things as-is, to avoid breaking non-compliant servers.
Mar 10 2013,
Aug 25 2015,
Archiving unconfirmed issues, which have not been modified (commented on, updated, etc...) in over 2 years.
Sign in to add a comment