Summary: | cannot read compressed content directly | ||
---|---|---|---|
Product: | WebKit | Reporter: | Baptiste Mille-Mathias <baptiste.millemathias> |
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | mrowe |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Linux |
Description
Baptiste Mille-Mathias
2009-06-06 01:46:55 PDT
I don't think the libsoup backend currently supports "Content-Encoding: gzip". That server appears to be unconditionally sending content with that content-encoding, even when the client does not include "gzip" in the "Accept-Encoding" header. I think that's technically a violation of the RFC. Boo. Right, since the Content-Type here is 'text/plain' I think this is just the server ignoring us when we say we don't support 'gzip' encoding, and that this would just work if the server wasn't buggy or if we supported that. Let's mark this as a dupe of 25855. *** This bug has been marked as a duplicate of 25855 *** |