Stuart, The behavior of this server appears to be consistent with a server that has been configured to require SSL client authentication.
I suspect that it is starting another handshake because the SSL session that was reused was one that had never done client authentication. If that is so, then suppressing SSL session reuse won't solve anything. So, I think it is more likely that this problem is due to server configuration than to SSL session reuse. -- Nelson Bolyard Netscape Disclaimer: I speak for myself, not for Netscape
