Can anyone help by explaining how the session cache works? We have a web site supported by two servers using a content switch to load balance. The content switch goes sticky on SSL id. We are discovering that when two people use SSL at the same time that towards the end of the SSL session the content switch suddenly routes one session to the other machine thus causing an error because the machine doesn't know anything about the session.
I have looked at the ssl_engine logs and found that it wants to give a session a new id even though the user is sending requests within the SSLCacheTimeout time. Does the time out last from the start of the session to the end or does it last from request to request? Does the browser affect what happens? I have seen discussion about nokeepalive with MSIE. Would this affect it? Any help appreciated. Mike Bray SBS UK. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
