httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Kosut <>
Subject Re: [PATCH] buff.c bug fix
Date Sat, 25 Jan 1997 09:51:40 GMT
On Sat, 25 Jan 1997, Marc Slemko wrote:

> >Netscape Navigator 2.0 (and possibly later versions) have a bug
> >where if the end of the body of a response message was in the same
> >(256-byte) read as a header, then it would not properly return the
> >document to user control - it would hang until the kept-alive
> >connection timed out.
> >
> >We fixed this by adding an fflush() after the headers were sent,
> >causing Netscape to read the body on another read, but this caused a
> >performance decrease, as an fflush() takes a while on most systems. We
> >ended up only flushing for persistent connections, which is okay,
> >assuming that the benefit from the persistent connection is greater
> >than the slowdown from the flushed buffer (which it probably is).

We actually took this flush (which turned into a bflush later) out,
since Navigator 3 doesn't have this problem (I think), and we don't
serve (or at least, don't recommend serving) persistent connections to
Navigator 2.

Alexei Kosut <>      The Apache HTTP Server

View raw message