generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

More interdependencies with respect to shutdown behaviour.

Browse Source
This commit is contained in:
Lutz Jänicke
2001-08-20 14:34:16 +00:00
parent a403188f92
commit d93eb21c7c
4 changed files with 35 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/ssl/SSL_write.pod
View File

@@ -78,8 +78,18 @@ 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<ret> to find out, whether an error occurred.
The write operation was not successful, because the write side of the
SSL connection was shut down (the SSL_SENT_SHUTDOWN flag in the shutdown
state is set) by calling L<SSL_shutdown(3)|SSL_shutdown(3)> or
L<SSL_set_shutdown(3)|SSL_set_shutdown(3)>. It is also possible, that the
underlying connection was closed.
Call SSL_get_error() with the return value B<ret> 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 E<lt>0