From f05735c8c932dc9cd591a1ef9b1140f65da5a7aa Mon Sep 17 00:00:00 2001 From: =?utf8?q?Lutz=20J=C3=A4nicke?= Date: Sat, 12 May 2001 09:49:46 +0000 Subject: [PATCH] Clarify behaviour with respect to SSL/TLS records. --- doc/ssl/SSL_read.pod | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/ssl/SSL_read.pod b/doc/ssl/SSL_read.pod index 7db5ee0a22..0db51452be 100644 --- a/doc/ssl/SSL_read.pod +++ b/doc/ssl/SSL_read.pod @@ -31,6 +31,18 @@ L or SSL_set_accept_state() must be used before the first call to an SSL_read() or L function. +SSL_read() works based on the SSL/TLS records. The data are received in +records (with a maximum record size of 16kB for SSLv3/TLSv1). Only when a +record has been completely received, it can be processed (decryption and +check of integrity). Therefore data that was not retrieved at the last +call of SSL_read() can still be buffered inside the SSL layer and will be +retrieved on the next call to SSL_read(). If B is higher than the +number of bytes buffered, SSL_read() will return with the bytes buffered. +If no more bytes are in the buffer, SSL_read() will trigger the processing +of the next record. Only when the record has been received and processed +completely, SSL_read() will return reporting success. At most the contents +of the record will be returned. + If the underlying BIO is B, SSL_read() will only return, once the read operation has been finished or an error occurred, except when a renegotiation take place, in which case a SSL_ERROR_WANT_READ may occur. -- 2.25.1