W3C home > Mailing lists > Public > www-validator-cvs@w3.org > July 2012

[Bug 17768] bzip2 encoding not recognized when content encoding field is "bzip2" (instead of "x-bzip2")

From: <bugzilla@jessica.w3.org>
Date: Fri, 13 Jul 2012 14:32:39 +0000
Message-Id: <E1Spgv9-0003qg-Lp@jessica.w3.org>
To: www-validator-cvs@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17768

Ville Skytt <ville.skytta@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Ville Skytt <ville.skytta@iki.fi> 2012-07-13 14:32:39 UTC ---
For some reason, when the validator says it supports the x-bzip2 encoding
(cannot verify on validator.w3.org but it does on my local box), the server
decides to send back bzip2 which doesn't seem correct; bzip2 is not a
registered content-coding value:

http://tools.ietf.org/html/rfc2616#section-3.5
http://www.iana.org/assignments/http-parameters/http-parameters.xml

I suspect it'd work if the server sent x-bzip2, but I cannot verify that. On my
local box for some reason bzip2 works just fine with the validator, I guess
this might be because of differences in libwww-perl versions which is the
library handling the response decoding. Anyway, I don't think this is a bug in
the validator nor libwww-perl but the server or its config.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 13 July 2012 14:32:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:50 UTC