ssl - improve documentation on mbedtls_ssl_read and PEER_CLOSE_NOTIFY
Add a description of MBEDTLS_ERR_SSL_PEER_CLOSE_NOTIFY to the documentation, as suggested by hanno-arm. Signed-off-by: Andrzej Kurek <andrzej.kurek@arm.com>
This commit is contained in:
parent
21d1cbccda
commit
03da0846df
1 changed files with 8 additions and 1 deletions
|
@ -3739,7 +3739,14 @@ int mbedtls_ssl_renegotiate( mbedtls_ssl_context *ssl );
|
|||
*
|
||||
* \return The (positive) number of bytes read if successful.
|
||||
* \return \c 0 if the read end of the underlying transport was closed
|
||||
* - in this case you must stop using the context (see below).
|
||||
* without sending a CloseNotify beforehand, which might happen
|
||||
* because of various reasons (internal error of an underlying
|
||||
* stack, non-conformant peer not sending a CloseNotify and
|
||||
* such) - in this case you must stop using the context
|
||||
* (see below).
|
||||
* \return #MBEDTLS_ERR_SSL_PEER_CLOSE_NOTIFY if the underlying
|
||||
* transport is still functional, but the peer has
|
||||
* acknowledged to not send anything anymore.
|
||||
* \return #MBEDTLS_ERR_SSL_WANT_READ or #MBEDTLS_ERR_SSL_WANT_WRITE
|
||||
* if the handshake is incomplete and waiting for data to
|
||||
* be available for reading from or writing to the underlying
|
||||
|
|
Loading…
Reference in a new issue