Lines Matching refs:sent
59 A close_notify shutdown alert message is sent to the peer.
93 return B<SSL_ERROR_ZERO_RETURN>), after all application data sent by the peer
98 not call SSL_shutdown() in this case, a close_notify alert will not be sent and
112 received from the peer, or because a close_notify alert message needs to be sent
119 process is complete (with a close_notify alert having both been sent and
132 sent by the peer using L<SSL_read(3)>.
202 that no more data is going to be sent. This requires an application protocol
203 which indicates unambiguously when all data has been sent.
208 reads, OpenSSL may never process new SSL/TLS session tickets sent by the server.
269 could not yet be transmitted, or which was sent but lost in the network, may not
285 application has been sent to the peer, and until the receipt of all such data is
306 to ensure that any connection closure notification sent to the peer was
364 may still be sent to the peer in any time spent waiting before the peer closes
384 For TLS and DTLS, this means that a close_notify alert has been sent but the
388 sent but the connection closure process has not yet completed.
398 For TLS and DTLS, this means that a close_notify alert was sent and the peer's
