| SSL_connect.pod (76866) | SSL_connect.pod (89837) |
|---|---|
| 1=pod 2 3=head1 NAME 4 5SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server 6 7=head1 SYNOPSIS 8 --- 20 unchanged lines hidden (view full) --- 29return value of SSL_connect() will yield B<SSL_ERROR_WANT_READ> or 30B<SSL_ERROR_WANT_WRITE>. The calling process then must repeat the call after 31taking appropriate action to satisfy the needs of SSL_connect(). 32The action depends on the underlying BIO. When using a non-blocking socket, 33nothing is to be done, but select() can be used to check for the required 34condition. When using a buffering BIO, like a BIO pair, data must be written 35into or retrieved out of the BIO before being able to continue. 36 | 1=pod 2 3=head1 NAME 4 5SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server 6 7=head1 SYNOPSIS 8 --- 20 unchanged lines hidden (view full) --- 29return value of SSL_connect() will yield B<SSL_ERROR_WANT_READ> or 30B<SSL_ERROR_WANT_WRITE>. The calling process then must repeat the call after 31taking appropriate action to satisfy the needs of SSL_connect(). 32The action depends on the underlying BIO. When using a non-blocking socket, 33nothing is to be done, but select() can be used to check for the required 34condition. When using a buffering BIO, like a BIO pair, data must be written 35into or retrieved out of the BIO before being able to continue. 36 |
| 37When using a generic method (see L<SSL_CTX_new(3)|SSL_CTX_new(3)>), it 38is necessary to call L<SSL_set_connect_state(3)|SSL_set_connect_state(3)> 39before calling SSL_connect() to explicitly switch the B<ssl> to client 40mode. 41 | |
| 42=head1 RETURN VALUES 43 44The following return values can occur: 45 46=over 4 47 48=item 1 49 --- 27 unchanged lines hidden --- | 37=head1 RETURN VALUES 38 39The following return values can occur: 40 41=over 4 42 43=item 1 44 --- 27 unchanged lines hidden --- |