X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=doc%2Fssl%2FSSL_write.pod;h=e013c12d5254b0d4d08bb0d6ef47972994b72ada;hb=5a84b7fc2db33cdefc5a7b62f0169f2c08fb3d9b;hp=da66f0f056fc2be2e63b90e7dfea8fc498a2ced1;hpb=7abe76e1bdb50ac8cfc54a8e28e9275aeb64c84d;p=oweals%2Fopenssl.git diff --git a/doc/ssl/SSL_write.pod b/doc/ssl/SSL_write.pod index da66f0f056..e013c12d52 100644 --- a/doc/ssl/SSL_write.pod +++ b/doc/ssl/SSL_write.pod @@ -65,6 +65,9 @@ When an SSL_write() operation has to be repeated because of B or B, it must be repeated with the same arguments. +When calling SSL_write() with num=0 bytes to be sent the behaviour is +undefined. + =head1 RETURN VALUES The following return values can occur: @@ -78,8 +81,14 @@ bytes actually written to the TLS/SSL connection. =item 0 -The write operation was not successful. Call SSL_get_error() with the return -value B to find out, whether an error occurred. +The write operation was not successful. Probably the underlying connection +was closed. Call SSL_get_error() with the return value B to find out, +whether an error occurred or the connection was shut down cleanly +(SSL_ERROR_ZERO_RETURN). + +SSLv2 (deprecated) does not support a shutdown alert protocol, so it can +only be detected, whether the underlying connection was closed. It cannot +be checked, why the closure happened. =item E0