You are viewing a plain text version of this content. The canonical link for it is here.

Posted to apache-bugdb@apache.org by Brian Behlendorf <br...@hyperreal.org> on 1998/05/07 01:23:50 UTC

Re: protocol/2107: Additional arguments for fixing PR#1464 ("Range: 0-" bug)

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 always send "Accept-Range: bytes" when an ETag and
>Last-Modified header are sent.  Thoughts?

Oh yeah, let me know if www.apache.org behaves how you'd like it to behave :)

	Brian


--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
pure chewing satisfaction                                  brian@apache.org
                                                        brian@hyperreal.org

Re: protocol/2107: Additional arguments for fixing PR#1464 ("Range: 0-" bug)

Posted by Андрей Чернов <ac...@nagual.pp.ru>.

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 can easily be changed - I currently think the way
> >to change it is just to always send "Accept-Range: bytes" when an ETag and
> >Last-Modified header are sent.  Thoughts?

I agree with this variant. It seems the same thing should be fixed for
v1.2.6 too, but I not check yet.

> Oh yeah, let me know if www.apache.org behaves how you'd like it to behave :)

Yes, thanx.

-- 
Andrey A. Chernov
http://www.nagual.pp.ru/~ache/
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y