X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=blobdiff_plain;f=doc%2Fman3%2FSSL_shutdown.pod;h=34469bae372863789f2dcc50b27e3626e650c01d;hp=25191130ae1ae300207fd6f307d67edb48853af9;hb=09b90e0ed7915809fcd4ee1e250d881b77d06d45;hpb=454afd9866300b984306c5b565a9d55568a5bc50 diff --git a/doc/man3/SSL_shutdown.pod b/doc/man3/SSL_shutdown.pod index 25191130ae..34469bae37 100644 --- a/doc/man3/SSL_shutdown.pod +++ b/doc/man3/SSL_shutdown.pod @@ -83,8 +83,10 @@ message, otherwise an unexpected EOF will be reported. There are implementations that do not send the required close_notify alert. If there is a need to communicate with such an implementation, and it's clear that all data has been received, do not wait for the peer's close_notify alert. -Waiting for the close_notify alert when the peer just closes the connection will -result in an error being generated. +Waiting for the close_notify alert when the peer just closes the connection +will result in an error being generated. +The error can be ignored using the B. +For more information see L. =head2 First to close the connection @@ -159,7 +161,7 @@ It can also occur when not all data was read using SSL_read(). L, L, L, L, -L, +L, L L, L, L, L