Tweak the SSL_read()/SSL_write() text based on feedback received.

Reviewed-by: Rich Salz <rsalz@openssl.org>
This commit is contained in:
Matt Caswell 2016-10-26 20:59:49 +01:00
parent 54105ddd23
commit ed9fa2c74b
2 changed files with 3 additions and 3 deletions

View File

@ -92,8 +92,8 @@ Success means that 1 or more application data bytes have been read from the SSL
connection. Failure means that no bytes could be read from the SSL connection. connection. Failure means that no bytes could be read from the SSL connection.
Failures can be retryable (e.g. we are waiting for more bytes to Failures can be retryable (e.g. we are waiting for more bytes to
be delivered by the network) or non-retryable (e.g. a fatal network error). In be delivered by the network) or non-retryable (e.g. a fatal network error). In
the event of a failure call L<SSL_get_error(3)> to find out the reason and if the event of a failure call L<SSL_get_error(3)> to find out the reason which
the call is retryable or not. indicates whether the call is retryable or not.
For SSL_read() and SSL_peek() the following return values can occur: For SSL_read() and SSL_peek() the following return values can occur:

View File

@ -80,7 +80,7 @@ no bytes could be written to the SSL connection (if
SSL_MODE_ENABLE_PARTIAL_WRITE is in use). Failures can be retryable (e.g. the SSL_MODE_ENABLE_PARTIAL_WRITE is in use). Failures can be retryable (e.g. the
network write buffer has temporarily filled up) or non-retryable (e.g. a fatal network write buffer has temporarily filled up) or non-retryable (e.g. a fatal
network error). In the event of a failure call L<SSL_get_error(3)> to find out network error). In the event of a failure call L<SSL_get_error(3)> to find out
the reason and if the call is retryable or not. the reason which indicates whether the call is retryable or not.
For SSL_write() the following return values can occur: For SSL_write() the following return values can occur: