1=pod 2 3=head1 NAME 4 5SSL_write - write bytes to a TLS/SSL connection. 6 7=head1 SYNOPSIS 8 --- 36 unchanged lines hidden (view full) --- 45B<SSL_ERROR_WANT_WRITE>. As at any time a re-negotiation is possible, a 46call to SSL_write() can also cause read operations! The calling process 47then must repeat the call after taking appropriate action to satisfy the 48needs of SSL_write(). The action depends on the underlying BIO. When using a 49non-blocking socket, nothing is to be done, but select() can be used to check 50for the required condition. When using a buffering BIO, like a BIO pair, data 51must be written into or retrieved out of the BIO before being able to continue. 52 |
53SSL_write() will only return with success, when the complete contents 54of B<buf> of length B<num> has been written. This default behaviour 55can be changed with the SSL_MODE_ENABLE_PARTIAL_WRITE option of 56L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)>. When this flag is set, 57SSL_write() will also return with success, when a partial write has been 58successfully completed. In this case the SSL_write() operation is considered 59completed. The bytes are sent and a new SSL_write() operation with a new 60buffer (with the already sent bytes removed) must be started. 61A partial write is performed with the size of a message block, which is 6216kB for SSLv3/TLSv1. 63 |
64=head1 WARNING 65 66When an SSL_write() operation has to be repeated because of 67B<SSL_ERROR_WANT_READ> or B<SSL_ERROR_WANT_WRITE>, it must be repeated 68with the same arguments. 69 70=head1 RETURN VALUES 71 --- 31 unchanged lines hidden --- |