[Webkit-unassigned] [Bug 25855] [GTK] Should support proper Content Encoding

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 21 10:33:49 PDT 2009


--- Comment #6 from Gustavo Noronha (kov) <gns at gnome.org>  2009-10-21 10:33:49 PDT ---
(In reply to comment #5)
> OK, since real Content-Encoding support is probably not coming until GNOME
> 2.30, and we're continuing to trip over sites that use "Content-Encoding: gzip"
> even though we send "Accept-Encoding: identity" (notably archive.org), maybe a
> gross hack is in order... what we'd do is, check from gotHeadersCallback if the
> response includes "Content-Encoding: gzip"; if so, disconnect from
> content-sniffed and got-chunk and connect to got-body. Wait until the got-body
> handler is called, unzip the body data all at once, call
> soup_content_sniffer_sniff() if necessary, and then belatedly emit all the
> webkit "signals". This would break incremental rendering of the data, but it
> would only be getting used on broken sites anyway.

I have been thinking the same. Are you planning to write such a patch, or
should I try to secure some time to get it done?

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list