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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 13 07:16:08 PDT 2009


Dan Winship <danw at gnome.org> changed:

           What    |Removed                     |Added
                 CC|                            |danw at gnome.org

--- Comment #5 from Dan Winship <danw at gnome.org>  2009-10-13 07:16:08 PDT ---
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.

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