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

[Bug 17768] New: 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:12:38 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-17768-169@http.www.w3.org/Bugs/Public/>

           Summary: bzip2 encoding not recognized when content encoding
                    field is "bzip2" (instead of "x-bzip2")
           Product: Validator
           Version: HEAD
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: check
        AssignedTo: dave.null@w3.org
        ReportedBy: soeren@solderware.net
         QAContact: www-validator-cvs@w3.org

Created attachment 1154
  --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1154
http response to reproduce the error

I just discovered that when the Server sets the the content-encoding header
field to "bzip2" instead of "x-bzip2", the validator fails to recognize the

An example to reproduce the Problem:

The server software is Lighttpd Version 1.4.31, its config is not modified with
respect to compression headers, so I assume that either lighttpd serves an
icorrect header or the validator has a bug.

Attached is the example response (including the header). You can reproduce the
problem with netcat: "cat resp-incorrect | nc -l -p 8080" and then point the
validator to http://your.ip:8080/

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:12:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:56 UTC