Some servers assume clients can handle content encodings such as gzip. This is something I intended to fix some time ago, but got distracted and forgot. I was reminded by a bug report in the Debian package: http://bugs.debian.org/529271.
Created attachment 30446 [details] Force identity as content encoding WebCore/ChangeLog | 10 ++++++++++ .../platform/network/soup/ResourceHandleSoup.cpp | 5 +++++ 2 files changed, 15 insertions(+), 0 deletions(-)
Comment on attachment 30446 [details] Force identity as content encoding r=me. But please do file a separate (tracking) bug for a proper content-encoding support in webkitgtk/libsoup so we don't forget about it.
(In reply to comment #2) > (From update of attachment 30446 [details] [review]) > r=me. But please do file a separate (tracking) bug for a proper > content-encoding support in webkitgtk/libsoup so we don't forget about it. > Done: https://bugs.webkit.org/show_bug.cgi?id=25855 It points to the GNOME bug, and to this one.
Landed as r43832.