I have ported SSL to a platform where I cannot easily cache a session (CICS). The server is treating every connection as brand new. As I understand the specification, this should be okay as long as the Server Hello message does not contain a session id. Everything works fine under Netscape. With MSIE, the initial request works. However, if I make a subsequent request within a few minutes, the browser claims that there is a problem with the SSL connection as soon as the server sends the certificate. A subsequent request after a few minutes works fine. I have carefully examined the certificate message, and there is nothing wrong with it. I have also verified that MSIE is not returning a session id in the subsequent Client Hello message. Does anybody have any idea what is going on? Thanks, Tom Damon ===== __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
