Richard Lynch wrote:
I *think* both client and server have to agree/support keep-alive, and
both have to be ready for the other guy to close the connection even
though they agreed in advance to keep-alive.
So you can use keep-alive, and it can work nifty, but ya gotta be
ready for the server/client to claim to support keep-alive and they're
gonna send you a close, and you gotta do the right thing.
Yep, all true.
I found the root of the problem. Much simpler than I'd imagined... Turns
out that Debian Sarge puts the following entry in
/etc/apache2/mods-available/mod_ssl.conf:
<IfModule mod_ssl.c>
...
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ...
...
</IfModule>
Unfortunately, that SetEnvIf line seems to disable keepalives in http
_and_ https, so long as mod_ssl is loaded - IMHO, it should be in the
vhost...
jon
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
