On Mon, 25 Mar 2002, Mads Toftum wrote: > The defaults are nokeepalive IIRC - if that affects the session, then > shouldn't it cut the session short even after the initial request?
nokeepalive doesn't really imply no session caching at all... that's not exactly what I meant to say. What I was trying to say was that IE doesn't deal well with sessions in general, which is why kept-alive sessions cause even more headaches -- IE just does bad things with them. I can't be much more specific than that because I haven't studied it in depth... but I just feel like things that would make IE behave better with sessions in general might make it do the right thing the server asks for a renegotation in this case. > Setting SSLLogLevel to something like debug and looking for cache > hits/misses would probably be a good place to start. This and testing with/without load balancing both sound like a good plan... --Cliff -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
