I received this bug report from a debian user.
It seems like a valid problem.
Comments?
Paul Slootman
On Fri 14 Sep 2001, Kalle Olavi Niemitalo wrote:
:
: I've set reply-compressed-data=yes in the Options section of
: wwwoffle.conf. This should make WWWOFFLE send compressed data
: to the client if the client supports that. So it does, but
: it can send the data in an encoding that the client doesn't
: support:
:
: kalle@Astalo:~$ nc localhost 8080
: GET /not-there HTTP/1.0
: Accept-Encoding: gzip
:
: HTTP/1.0 404 WWWOFFLE Page Not Found
: Server: WWWOFFLE/2.6d
: Date: Fri, 14 Sep 2001 16:38:54 GMT
: Content-type: text/html
: Connection: close
: Content-Encoding: x-gzip
: Proxy-Connection: close
:
: [binary drivel omitted]
:
: I asked for the "gzip" encoding, but WWWOFFLE replied with an
: "x-gzip" encoding. Those may be the same format but you cannot
: expect the client to know that. Indeed, MS Internet Explorer
: version 5.00.2614.3500 asks for "Accept-Encoding: gzip, deflate"
: and cannot parse the body with "Content-Encoding: x-gzip".
:
: Please change WWWOFFLE so that it remembers whether the client
: asked for "gzip" or "x-gzip", and uses the same name in the
: response.
