SSL_connect(3) | OpenSSL | SSL_connect(3) |
If the underlying BIO is blocking, SSL_connect() will only return once the handshake has been finished or an error occurred.
If the underlying BIO is non-blocking, SSL_connect() will also return when the underlying BIO could not satisfy the needs of SSL_connect() to continue the handshake, indicating the problem by the return value -1. In this case a call to SSL_get_error() with the return value of SSL_connect() will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. The calling process then must repeat the call after taking appropriate action to satisfy the needs of SSL_connect(). The action depends on the underlying BIO. When using a non-blocking socket, nothing is to be done, but select() can be used to check for the required condition. When using a buffering BIO, like a BIO pair, data must be written into or retrieved out of the BIO before being able to continue.
1. | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established. |
2. | The TLS/SSL handshake was not successful but was shut down controlled and by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the return value ret to find out the reason. |
3. |
<0 |
Around line 49: | You have '=item 0' instead of the expected '=item 2' |
Around line 55: | Expected '=item 3' |
July 20, 2009 | 1.0.1-dev |