httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Ames <>
Subject Re: [PATCH] daedalus coredump from 2.0.35c
Date Wed, 10 Apr 2002 15:47:59 GMT
OK, I had a look at RFC 2616.  The current ordering now makes sense to me,
because the Content-Length: header we put on the wire has to be the the length
of the partial GET limited by the ranges, not the length of the whole thing if
there weren't ranges.  It's clearly explained in section 10.2.7.

Ryan Bloom wrote:

> > Clearly there is a bug.  As I explained, with the current ordering, the
> > byterange filter can take itself out of the chain the first time it is
> > called,
> > before the true content length is known.
> The problem here is that the byterange filter is removing itself before
> it should.  Moving it shouldn't actually solve this problem at all.  The
> byterange filter should ONLY remove itself if it looks at the request
> headers, and there is no Range header at all.

Well, that's not what it's doing, but it should be pretty easy to fix.


View raw message