From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Description of problem: Version-Release number of selected component (if applicable): tux-2.2.4-1, kernel-2.4.9-e.25 How reproducible: Always Steps to Reproduce: 1. Add content 2. gzip the content 3. request content $ curl -I http://host/file.html 4. request with accept encoding curl -I -H "Accept-Encoding: gzip" http://host/file.html Actual Results: * Without accept encoding * $ curl -I http://host/file.html HTTP/1.1 200 OK Content-Type: text/html Connection: Keep-Alive Date: Mon, 17 Nov 2003 12:58:04 GMT Server: TUX/2.0 (Linux) Content-Length: 5214 ETag: "5214-dpkjacpd" Accept-Ranges: bytes Last-Modified: Wed, 05 Nov 2003 14:02:27 GMT * With accept encoding * $ curl -I -H "Accept-Encoding: gzip" http://host/file.html HTTP/1.1 200 OK Content-Type: text/html Connection: Keep-Alive Date: Mon, 17 Nov 2003 12:58:09 GMT Content-Encoding: gzip Server: TUX/2.0 (Linux) Content-Length: 5214 ETag: "5214-dpkjacpd" Accept-Ranges: bytes Last-Modified: Wed, 05 Nov 2003 14:02:27 GMT Gzipped content is server and content length is less than 5214 bytes, but the header says that content length is 5214 bytes Expected Results: Content-length must indicate the length of compressed data Additional info:
Created attachment 100227 [details] patch against tux patch itself Fixes Content-Length problem for gzipped content
Patch is actually against latest tux patch found in RHEL 3.0 kernel rpm. If needed I can also sen patch against latest 2.1 kernel, but it should be quite straight forward thing to do.
ok, patch queued up for inclusion into RHEL3.
A fix for this problem has just been committed to the RHEL3 U4 patch pool this evening (in kernel version 2.4.21-20.5.EL).
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-550.html