Lines Matching refs:has
58 These functions are used to send and receive early data where TLSv1.3 has been
61 Early data can be sent if a session has previously been established with the
64 to send data from the server to the client when the client has not yet completed
67 Early data has weaker security properties than other data sent over an SSL/TLS
75 done before the full handshake has been completed. Specifically the client's
80 A server or client can determine whether the full handshake has been completed
107 SSL_write_early_data() call has completed successfully the client may interleave
120 A server may choose to ignore early data that has been sent to it. Once the
121 connection has been completed you can determine whether the server accepted or
128 connection for which early data has been enabled using
156 first call to SSL_read_early_data() if the client has not sent any early data,
161 Once the initial SSL_read_early_data() call has completed successfully (i.e. it
162 has returned SSL_READ_EARLY_DATA_SUCCESS or SSL_READ_EARLY_DATA_FINISH) then the
168 determine whether the handshake has completed or not. If the handshake is still
173 L<SSL_write(3)> until SSL_read_early_data() has returned with
174 SSL_READ_EARLY_DATA_FINISH. Once it has done so the connection to the client
179 attempt to complete the connection before SSL_read_early_data() has returned
218 The recv_max_early_data value also has an impact on early data that is accepted.
241 has been explicitly disabled using the SSL_OP_NO_ANTI_REPLAY option. See
252 the server before a full round trip of network traffic has occurred. Application
258 buffer outgoing TCP data if a TCP packet has already been sent which we have not
268 sent until a complete round trip with the server has occurred which defeats the
278 support this. For example, this can occur if a server has had its configuration
319 is called. This could result in a small amount of time where the session has
