X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=blobdiff_plain;f=doc%2Fssl%2FSSL_write.pod;h=8110161522a3ddea8657b5165692fb519f4444b8;hp=0a1adaba7327b2259d8b550911ee6be0e258cd92;hb=4ce7894c4ab87d7c635e45bf5ff8d1d729b79527;hpb=c19b6c922a6575974455404be3c1409de60fb1eb diff --git a/doc/ssl/SSL_write.pod b/doc/ssl/SSL_write.pod index 0a1adaba73..8110161522 100644 --- a/doc/ssl/SSL_write.pod +++ b/doc/ssl/SSL_write.pod @@ -2,7 +2,7 @@ =head1 NAME -SSL_read - write bytes to a TLS/SSL connection. +SSL_write - write bytes to a TLS/SSL connection. =head1 SYNOPSIS @@ -31,14 +31,14 @@ when the underlying BIO could not satisfy the needs of SSL_write() to continue the operation. In this case a call to SSL_get_error() with the return value of SSL_write() will yield B or B. As at any time a re-negotiation is possible, a -call to SSL_write() can also cause write operations! The calling process +call to SSL_write() can also cause read operations! The calling process then must repeat the call after taking appropriate action to satisfy the needs of SSL_write(). 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. -=head1 IMPORTANT +=head1 WARNING When an SSL_write() operation has to be repeated because of B or B, it must be repeated @@ -60,9 +60,9 @@ bytes actually written to the TLS/SSL connection. The write operation was not successful. Call SSL_get_error() with the return value B to find out, whether an error occurred. -=item -1 +=item E0 -The read operation was not successful, because either an error occurred +The write operation was not successful, because either an error occurred or action must be taken by the calling process. Call SSL_get_error() with the return value B to find out the reason.