On Wed, May 06, 1998 at 04:23:50PM -0700, Brian Behlendorf wrote:
> At 03:28 PM 5/6/98 -0700, Brian Behlendorf wrote:
> >First I wanted to say, you're right, a request with a "Range: bytes=0-" in
> >the header will not have a "Accept-Range: bytes" in the response, in the
> >current CVS code. That
At 03:28 PM 5/6/98 -0700, Brian Behlendorf wrote:
>First I wanted to say, you're right, a request with a "Range: bytes=0-" in
>the header will not have a "Accept-Range: bytes" in the response, in the
>current CVS code. That can easily be changed - I currently think the way
>to change it is just to
First I wanted to say, you're right, a request with a "Range: bytes=0-" in
the header will not have a "Accept-Range: bytes" in the response, in the
current CVS code. That can easily be changed - I currently think the way
to change it is just to always send "Accept-Range: bytes" when an ETag and
L
The following reply was made to PR protocol/2107; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]>
To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= <[EMAIL PROTECTED]>
Cc: Apache bugs database <[EMAIL PROTECTED]>
Subject: Re: protocol/2107: Additional arguments for fixi
On Wed, 6 May 1998, Андрей Чернов wrote:
> On Wed, May 06, 1998 at 04:44:02AM -, [EMAIL PROTECTED] wrote:
> > > 3) RFC 2068 eslecially points that the server MUST return 206 for ANY
> > > Range: request.
> >
> > Where? That's not even possible - the resource might not even exist, so how
> >
On Wed, May 06, 1998 at 04:44:02AM -, [EMAIL PROTECTED] wrote:
> > 3) RFC 2068 eslecially points that the server MUST return 206 for ANY
> > Range: request.
>
> Where? That's not even possible - the resource might not even exist, so how
> can it return a 206 instead of a 404? I'm not being
[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. ]
Synopsis: Additional arguments for fixing PR#1464 ("Range: 0-" bu
>Number: 2107
>Category: protocol
>Synopsis: Additional arguments for fixing PR#1464 ("Range: 0-" bug)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible:apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Dat
