Lines Matching +full:read +full:- +full:out

6 - read bytes from a TLS/SSL connection
20 SSL_read_ex() and SSL_read() try to read B<num> bytes from the specified B<ssl>
22 actually read in B<*readbytes>.
26 the read, so that a subsequent call to SSL_read_ex() or SSL_read() will yield
31 In the paragraphs below a "read function" is defined as one of SSL_read_ex(),
34 If necessary, a read function will negotiate a TLS/SSL session, if not already
36 peer requests a re-negotiation, it will be performed transparently during
37 the read function operation. The behaviour of the read functions depends on the
43 invocation of a read function.
45 The read functions work based on the SSL/TLS records. The data are received in
48 Therefore, data that was not retrieved at the last read call can still be
49 buffered inside the SSL layer and will be retrieved on the next read
50 call. If B<num> is higher than the number of bytes buffered then the read
52 buffer, the read functions will trigger the processing of the next record.
53 Only when the record has been received and processed completely will the read
56 of the underlying transport (e.g. TCP), it may be necessary to read several
57 packets from the transport layer before the record is complete and the read call
60 If B<SSL_MODE_AUTO_RETRY> has been switched off and a non-application data
61 record has been processed, the read function can return and set the error to
64 If read ahead was set using L<SSL_CTX_set_read_ahead(3)>, there might also still
68 If the underlying BIO is B<blocking>, a read function will only return once the
69 read operation has been finished or an error occurred, except when a
70 non-application data record has been processed and B<SSL_MODE_AUTO_RETRY> is
72 Note that if B<SSL_MODE_AUTO_RETRY> is set and only non-application data is
75 If the underlying BIO is B<nonblocking>, a read function will also return when
79 return value of the read function will yield B<SSL_ERROR_WANT_READ> or
81 As at any time it's possible that non-application data needs to be sent,
82 a read function can also cause write operations.
84 to satisfy the needs of the read function.
89 retrieved out of the BIO before being able to continue.
91 L<SSL_pending(3)> can be used to find out whether there
93 In this case the read function can be called without blocking or actually
99 Success means that 1 or more application data bytes have been read from the SSL
101 Failure means that no bytes could be read from the SSL connection.
103 be delivered by the network) or non-retryable (e.g. a fatal network error).
104 In the event of a failure call L<SSL_get_error(3)> to find out the reason which
113 The read operation was successful.
114 The return value is the number of bytes actually read from the TLS/SSL
119 The read operation was not successful, because either the connection was closed,
121 Call L<SSL_get_error(3)> with the return value B<ret> to find out the reason.
123 Old documentation indicated a difference between 0 and -1, and that -1 was
125 You should instead call SSL_get_error() to find out if it's retryable.
145 Copyright 2000-2020 The OpenSSL Project Authors. All Rights Reserved.