On 2004.12.08, Bernd Eidenschink <[EMAIL PROTECTED]> wrote:
>
> last year there was a thread concerning a 'weird 0 length problem':
> Wojciech Kocjan discovered requests served with a Content-Length
> of "0". As I see it there was neither a solution to that problem nor a
> bug to be found at that time.
While working on nsjk2, I came across a bug in nsd/adprequest.c. Here's
the relevant ChangeLog entry:
2004-11-17 Dossy Shiobara <[EMAIL PROTECTED]>
* nsd/adprequest.c (1.16.2.1): Don't send Content-Length if
streaming is on. Backport from HEAD.
This change made it into AOLserver 4.0.9. No bug was filed for it at
SF and I didn't bother filing one before fixing this.
The essence of the bug is when ADP streaming is on (ns_adp_stream),
instead of omitting the Content-Length: header in the HTTP response as
it SHOULD do, it sends a "Content-Length: 0" instead which is wrong.
The change mentioned above fixes this bug.
If there's another "weird 0 length problem" bug, I'm unaware of it. In
my access logs, the only time I see 0-byte responses are for HEAD
requests (where 0-byte response is correct), and for actual files that
are 0-bytes in size.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
