Hi,
Does somebody know old issues with Netscape 4.x and SSL keepalive ? I actually have an httpd-2.0 reverse proxy, and an IIS backend.
Netscape connected directly on IIS is runnig well, keepalive is ok.
Netscape connected throught a netscape proxy is running well, keepalive is ok.
Netscape connected to Apache 2.0 reverse proxy is running slow because there is no keepalive and each connection is replaying an SSL Handshake.
Netscape send header keep-alive, but SSL close the connection after each request.
I read issues on close_notify stuff with the standard shutdown of ssl connection. I tryied to play with accurate instead of standard but i was not able to get something working. It's really strange that Netscape must renegotiate each time it do a connection.
Matthieu
