httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Hartill <r...@imdb.com>
Subject WWW Form Bug Report: "Keep Alive Timeout does not work on server." on Solaris 2.x (fwd)
Date Fri, 22 Nov 1996 16:27:19 GMT

Keepalive is triggered only when the browser agrees, right ?

Anyone know what's he's talking about then ?

----- Forwarded message from dvella@kemmunet.net.mt -----

Message-Id: <199611221127.DAA22726@taz.hyperreal.com>
From: dvella@kemmunet.net.mt
To: apache-bugs%apache.org@organic.com
Date: Fri Nov 22  3:27:47 1996
Subject: WWW Form Bug Report: "Keep Alive Timeout does not work on server." on Solaris 2.x

Submitter: dvella@kemmunet.net.mt
Operating system: Solaris 2.x, version: 
Version of Apache Used: apache 1.1.1
Extra Modules used: mod_proxy mod_php
URL exhibiting problem: 

Symptoms:
--
When the Keep-Alive directive is enabled, many browsers
(probably those that don't support it) are not
timd out.  Since there are many of these,the 
Apache server quickly reaches its maximum Clients
(MaxClients) figures are refutes any other connections
although in actual fact only a few (or none!) would
be using it.
I read that Keep-Alive is not supported on many
browsers.  Is this what happens with them?
When I disabled Keep-Alives, the Timeout directive
worked fine.

Thanks

--

Backtrace:
--

--

----- End of forwarded message from dvella@kemmunet.net.mt -----

-- 
Rob Hartill.       Internet Movie Database Ltd.    http://www.imdb.com/  

Mime
View raw message