This is on iOS, which can do some fairly aggressive things when you background an app, including (apparently) locally tearing down a socket connection.
What I'm seeing is SSL_read returning SSL_ERROR_WANT_READ forever. Tracking this down the stack, it's coming from BIO_sock_non_fatal_error returning 1 on ENOTCONN. At this point, ENOTCONN is fatal (I think). Not sure if it's as simple as making ENOTCONN fatal? I'm not expert enough on the state transitions here, i,e., if ENOTCONN is true before a connection is made and it's possible to go through this path, than making ENOTCONN fatal wouldn't work. That would require some other way of correlating with the connection state in order to determine fatality?______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
