diff options
author | Lutz Jänicke <jaenicke@openssl.org> | 2001-08-20 14:34:16 +0000 |
---|---|---|
committer | Lutz Jänicke <jaenicke@openssl.org> | 2001-08-20 14:34:16 +0000 |
commit | d93eb21c7c1e39db098a7f1331a75cc95a783c2a (patch) | |
tree | cbf9558be88e1cc24ed820c22b8c54afb6c77d70 /doc/ssl/SSL_write.pod | |
parent | a403188f92101512d4d3e45bc7b8e047d283d9d2 (diff) |
More interdependencies with respect to shutdown behaviour.
Diffstat (limited to 'doc/ssl/SSL_write.pod')
-rw-r--r-- | doc/ssl/SSL_write.pod | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/doc/ssl/SSL_write.pod b/doc/ssl/SSL_write.pod index da66f0f056..7299f6e2ee 100644 --- a/doc/ssl/SSL_write.pod +++ b/doc/ssl/SSL_write.pod @@ -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 |