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

Posted to apache-bugdb@apache.org by Jeremy Elson <je...@circlemud.org> on 2001/11/15 09:30:32 UTC

Re: protocol/8549: 416 errors return Content-Length header followed by no content, causing client hang

Hi,

I submitted this bug, and patch to fix the bug, 4 weeks ago but
haven't seen any reply - did it get lost in the cracks? :-)

Best,
-Jer

submit@bugz.apache.org writes:
>Thank you very much for your problem report.
>It has the internal identification `protocol/8549'.
>The individual assigned to look at your
>report is: apache. 
>
>>Category:       protocol
>>Responsible:    apache
>>Synopsis:       416 errors return Content-Length header followed by no content, causing client hang
>>Arrival-Date:   Tue Oct 16 01:20:01 PDT 2001

Re: protocol/8549: 416 errors return Content-Length header followed by no content, causing client hang

Posted by "William A. Rowe, Jr." <wr...@covalent.net>.

From: "Jeremy Elson" <je...@circlemud.org>
Sent: Thursday, November 15, 2001 2:30 AM


> Hi,
> 
> I submitted this bug, and patch to fix the bug, 4 weeks ago but
> haven't seen any reply - did it get lost in the cracks? :-)

Setting the content length to zero seems very wrong.  I suspect we could
remove the content length header altogether, which should let the client
fall back on the chunking lengths, if implemented, or socket close.  Since
this is an exception condition, I don't suppose the HTTP/1.0-style socket 
close should have a necessarily negative impact on performance.

Thoughts?