>Number: 3951
>Category: protocol
>Synopsis: Range 0- ignored
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Tue Feb 23 13:40:00 PST 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.3, 1.3.4
>Environment:
Win32
>Description:
In a HTTP client code I wrote I send a dummy "Request 0-" header, in order to
see if the server responds with 206 and so determine if the request is
"restartable" at a later time. I noticed that Apache 1.3.3 and 1.3.4 respond
with 200 OK, ignoring my dummy Range header. By comparing the source code of
1.2.6 and 1.3.4 I found this line in the parse_byterange function
(http_protocol.c)
return (*start > 0 || *end < clength - 1);
>How-To-Repeat:
>Fix:
Is this behavior intentional? I think Range 0- does not violate HTTP/1.1, so
the code in my opinion should be
return (*start >= 0 || *end <= clength - 1);
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request ]
[from a developer. ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]
