It sounds like it's about time to break out Wireshark or another packet capture utility and see what the actual on-wire traffic is. Something, somewhere, is unhappy and isn't following the protocols.
-Kyle H On Mon, Jun 15, 2009 at 2:36 AM, chithuanand<chithuan...@yahoo.com> wrote: > > The server is Apache Tomcat . The server logs say that the response is sent. > But at the client, we are not able to read the response. Instead, the > SSL_read() is failing with the error "SSL_ERROR_SYSCALL" > > > > Is the server IIS? > > And do you get all of the response? > > Because IIS doesn't necessarily close SSL connections in a tidy manner - > it can give SSL_ERROR_SYSCALL. > > G. > > > > -- > View this message in context: > http://www.nabble.com/SSL_read%28%29-returns-SSL_ERROR_SYSCALL-tp23918379p24031564.html > Sent from the OpenSSL - User mailing list archive at Nabble.com. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-us...@openssl.org > Automated List Manager majord...@openssl.org > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
