httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: 304 and keepalive bug
Date Wed, 29 Jan 1997 08:04:29 GMT
But is my patch really the best way to do it?  Shouldn't all 300, 400, and
500 responses allow keepalive?  It's only 200s that don't have
content-length (and can't chunk encode) that I can think of which should
send Connection: close.  But I've never looked into this part of the
server very much. 

Dean

On Tue, 28 Jan 1997, Alexei Kosut wrote:

> On Tue, 28 Jan 1997, Dean Gaudet wrote:
> 
> > I tried with the patch below included and navigator was able to do
> > keepalive properly on 304 responses.  So this is definately an apache bug.
> > I'm not sure of the correct solution, that set_keepalive if() statement is
> > a monster mess.
> 
> It's not a bug - Apache's not required to support persistent
> connections at all. On the other hand, it's a nice feature, and I can
> see no reason why Apache shouldn't keep persistent connections alive.
> 
> +1 on your patch.
> 
> -- 
> ________________________________________________________________________
> Alexei Kosut <akosut@nueva.pvt.k12.ca.us>      The Apache HTTP Server
> URL: http://www.nueva.pvt.k12.ca.us/~akosut/   http://www.apache.org/
> 
> 


Mime
View raw message