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