Closed
Bug 479266
Opened 16 years ago
Closed 12 years ago
Should support nested content encodings
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
RESOLVED
DUPLICATE
of bug 717524
People
(Reporter: Biesinger, Unassigned)
Details
From RFC 2616 14.11:
If multiple encodings have been applied to an entity, the content
codings MUST be listed in the order in which they were applied.
We should support that. Currently our code looks like this:
735 const char *val = mResponseHead->PeekHeader(nsHttp::Content_Encoding);
736 if (gHttpHandler->IsAcceptableEncoding(val)) {
[...]
http://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/http/src/nsHttpChannel.cpp#735
The code should split the header into its separate values and apply a sequence of stream converters.
This would be useful for the case of SDCH, which uses:
Content-Encoding: sdch, gzip
Comment 1•12 years ago
|
||
This has been fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=717524
would mark this as a duplicate but i cannot seem to find the button,
or don't have permissions to, either way.
Comment 2•12 years ago
|
||
(In reply to Andrew from comment #1)
> This has been fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=717524
> would mark this as a duplicate but i cannot seem to find the button,
> or don't have permissions to, either way.
Change status to "RESOLVED" and then choose "DUPLICATE" for the resolution.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•