1=pod 2 3=head1 NAME 4 5SSL_get_error - obtain result code for TLS/SSL I/O operation 6 7=head1 SYNOPSIS 8 --- 55 unchanged lines hidden (view full) --- 64 65Caveat: Any TLS/SSL I/O function can lead to either of 66B<SSL_ERROR_WANT_READ> and B<SSL_ERROR_WANT_WRITE>. In particular, 67SSL_read() or SSL_peek() may want to write data and SSL_write() may want 68to read data. This is mainly because TLS/SSL handshakes may occur at any 69time during the protocol (initiated by either the client or the server); 70SSL_read(), SSL_peek(), and SSL_write() will handle any pending handshakes. 71 |
72=item SSL_ERROR_WANT_CONNECT, SSL_ERROR_WANT_ACCEPT |
73 74The operation did not complete; the same TLS/SSL I/O function should be 75called again later. The underlying BIO was not connected yet to the peer |
76and the call would block in connect()/accept(). The SSL function should be 77called again when the connection is established. These messages can only 78appear with a BIO_s_connect() or BIO_s_accept() BIO, respectively. |
79In order to find out, when the connection has been successfully established, 80on many platforms select() or poll() for writing on the socket file descriptor 81can be used. 82 83=item SSL_ERROR_WANT_X509_LOOKUP 84 85The operation did not complete because an application callback set by 86SSL_CTX_set_client_cert_cb() has asked to be called again. --- 28 unchanged lines hidden --- |