Red Hat Bugzilla – Bug 88575
Byte Range implementation fix
Last modified: 2007-04-18 12:52:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20030208
Description of problem:
There is a fix for apache bugzilla bugs #11601 and #18913 which should be
applied to Redhat until it can ship >= 2.0.44
Whenever an apache request does not return the file, eg 404, 401, 304, and the
request has a Range: header, the byterange code incorrectly does it's thing
anyway and does illogical things to the response.
Apache 2.0 CVS revision 1.463 of modules/http/http_protocol.c contains the patch
to fix it. Very minor change with a big effect on byte-range requests.
Here's the official diff:
Thanks, reapplying the patch by hand every time there's an erratum would be a pain.
Version-Release number of selected component (if applicable):
Prior to 2.0.44, using httpd-2.0.40-11
Steps to Reproduce:
1.# curl -i -r bytes=0-9 -z 'Sat, 21 Dec 2002 06:46:30 GMT'
2.run the command above with the current time stamp
Actual Results: If they are still running 2.0.40:
HTTP/1.1 416 Requested Range Not Satisfiable
Expected Results: If the time stamp is currect:
HTTP/1.1 304 Not Changed
Additional info: Also affects rh 9.0
Fix is being integrated for the next erratum. Thanks for filing the bug.
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.
It works great!