X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=doc%2Fssl%2FSSL_read.pod;h=f6c37f77e491d5d39c02a85bdd9922e0bc3e10b4;hp=6b47f2fbd1bb95e5834546dc4618bbaacde3f51d;hb=6d8566f2ebbd20a2f6e7ec656e299f5359138467;hpb=4e1b0d890489a1e13a3ea431de7dafda548c2d74;ds=sidebyside diff --git a/doc/ssl/SSL_read.pod b/doc/ssl/SSL_read.pod index 6b47f2fbd1..f6c37f77e4 100644 --- a/doc/ssl/SSL_read.pod +++ b/doc/ssl/SSL_read.pod @@ -83,11 +83,13 @@ bytes actually read from the TLS/SSL connection. =item 0 -The read operation was not successful, the SSL connection was closed by the -peer by sending a "close notify" alert. The SSL_RECEIVED_SHUTDOWN flag in -the ssl shutdown state is set (see L, -L). -Call SSL_get_error() with the return value B to find out, +The read operation was not successful. The reason may either be a clean +shutdown due to a "close notify" alert sent by the peer (in which case +the SSL_RECEIVED_SHUTDOWN flag in the ssl shutdown state is set +(see L, +L). It is also possible, that +the peer simply shut down the underlying transport and the shutdown is +incomplete. 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).