Okay guys, this is definately the bug we are seeing. I am testing a patch
now, and it will be committed in a few hours. Don't shoot the messenger
on this one. I just found the bug, I don't know how long it has been
there.
Ryan
On 7 Mar 2001, Jeff Trawick wrote:
> Cliff Woolley <[EMAIL PROTECTED]> writes:
>
> > On Wed, 7 Mar 2001 [EMAIL PROTECTED] wrote:
> >
> > > Mod_include is working correctly, as is the content-length filter, in all
> > > of my tests. The only time I don't get chunked responses for the
> > > content-length, is if I don't put "Transfer-Encoding: chunked" in the
> > > request headers.
> >
> > Hrm... I was under the impression that "Transfer-Encoding: chunked" means
> > that the *request* is chunked.
>
> yep (I assume you mean when that header field is provided on the request)
>
> > "TE: chunked" means that the *response*
> > may be chunked. Does the server not send a chunked response unless the
> > client sent a chunked request? Surely not, since many requests don't have
> > bodies to chunk in the first place.
>
> The server can send a chunked response for any 1.1 request. Using
> non-chunked (with content length) is preferable because it gives the
> client information for displaying status.
>
> --
> Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
> http://www.geocities.com/SiliconValley/Park/9289/
> Born in Roswell... married an alien...
>
>
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
