Lines Matching refs:SSL_read

20 …- [`SSL_read`, `SSL_read_ex`, `SSL_peek`, `SSL_peek_ex`](#-ssl-read----ssl-read-ex----ssl-peek----…
218 #### `SSL_read`, `SSL_read_ex`, `SSL_peek`, `SSL_peek_ex`
228 `SSL_read` will fail with `SSL_ERROR_ZERO_RETURN`.
231 stream has been reset, or the connection has terminated), calls to `SSL_read`
671 also signals the end of the stream. Thus, `SSL_read()` can still be used.
746  * and that any future SSL_read calls will return any residual data waiting to
760  * SSL_read will fail, though SSL_read may allow any  residual data waiting to
785  * stream via SSL_read will fail, though SSL_read may allow any residual
1137  *     consumption. `SSL_read` and `SSL_write` calls must be made on a QUIC
1157  *     bound as the default stream. Thereafter, calls to `SSL_read` will fail.
1622 before it calls `SSL_read` by definition is using a locally-initiated stream,
1624 We can use the ordering of initial calls to `SSL_read` and `SSL_write` to infer
1630 Supporting remotely-initiated streams (`SSL_read` called first) is a little
1632 initial call to `SSL_read` implying use of a remotely-initiated stream. However,
1658 If the local application calls `SSL_read()` before either of the above
1659 occur, `SSL_read()` fails as though no data is available until one