Bug #2443

Content-Encoding "bzip2" (instead of "x-bzip2")

Added by kai@bolay.de about 2 years ago. Updated almost 2 years ago.

Status:FixedStart date:2012-09-09
Priority:LowDue date:
Assignee:-% Done:

100%

Category:mod_compress
Target version:-
Missing in 1.5.x:No

Description

The W3C HTML validator has problems validating pages hosted by lighttpd - see https://www.w3.org/Bugs/Public/show_bug.cgi?id=17768

I've reproduced the issue with my server running lighttpd/1.4.26 with the stock configuration included with Ubuntu 10.04.1 LTS:

$ telnet localhost 80
Trying ::1...
Connected to localhost.localdomain.
Escape character is '^]'.
GET / HTTP/1.0
Accept-Encoding: x-bzip2

HTTP/1.0 200 OK
Vary: Accept-Encoding
Content-Encoding: bzip2
Last-Modified: Thu, 23 Apr 2009 21:45:28 GMT
ETag: "-316035401"
Content-Type: text/html
Accept-Ranges: bytes
Content-Length: 1727
Connection: close
Date: Sun, 09 Sep 2012 21:30:52 GMT
Server: lighttpd/1.4.26
[...]

The response to the bug report on the W3C site implies that the response should be "Content-Encoding: x-bzip2" and not "Content-Encoding: bzip2".

Can this be fixed via reconfiguration? And/or is this fixes with a more recent version of lighttpd? Thanks!

Associated revisions

Revision 2856
Added by stbuehler almost 2 years ago

detect "x-gzip"/"x-bzip2" as separate encodings, more strict encoding matching (fixes #2443)

History

#1 Updated by stbuehler almost 2 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset r2856.

Also available in: Atom