Lines Matching full:connection

5 SSL_shutdown, SSL_shutdown_ex - shut down a TLS/SSL or QUIC connection
24 SSL_shutdown() shuts down an active connection represented by an SSL object. I<ssl> B<MUST NOT> be …
46 connection; i.e., if L<SSL_get_error(3)> has returned B<SSL_ERROR_SYSCALL> or
67 These steps can occur in either order depending on whether the connection
77 Calling SSL_shutdown() only closes the write direction of the connection; the
80 until the peer decides to close the connection in turn. The peer might
84 SSL_shutdown() does not affect an underlying network connection such as a TCP
85 connection, which remains open.
144 (such that it returns 0) and then close the underlying connection without
153 connection.
158 peer of connection shutdown.
161 the underlying connection (e.g. a TCP connection) for further communication; in
175 SSL_shutdown() can be modified to set the connection to the "shutdown"
188 alert message but simply close the underlying transport (e.g. a TCP connection)
207 If a client application only writes to an SSL/TLS or DTLS connection and never
220 When used with a QUIC connection SSL object, SSL_shutdown() initiates a QUIC
228 provide additional information to the peer on the reason why a connection is
245 is copied and stored inside the QUIC connection SSL object and need not remain
256 SSL_shutdown_ex() (or SSL_shutdown()) for a given QUIC connection SSL object.
260 represents; for example, a UDP datagram provided to a QUIC connection as the
265 TLS/TCP connection, where reliable transmission of buffered data is the
267 QUIC connection SSL object or exits before completing the shutdown process using
274 whether during connection usage or during shutdown. If an application is not
303 Aspects of how QUIC handles connection closure must be taken into account by
304 applications. Ordinarily, QUIC expects a connection to continue to be serviced
306 to ensure that any connection closure notification sent to the peer was
308 RFC-compliant QUIC connection closure process could take of the order of
313 As such, there are two shutdown modes available to users of QUIC connection SSL
327 indicating the closure process is complete and the connection is now fully shut
332 In this mode, the peer is notified of connection closure on a best effort basis
334 know that the connection has terminated until the negotiated idle timeout (if
337 This will generally return 0 on success, indicating that the connection has not
355 waits until the peer initiates a shutdown or the connection otherwise becomes
359 If a locally initiated shutdown has already been triggered or the connection has
363 stream data cannot be flushed after a peer closes the connection. Stream data
365 the connection, though there is no guarantee of this.
369 SSL_shutdown() and SSL_shutdown_ex() block if the connection is configured in
387 For QUIC connection SSL objects, a CONNECTION_CLOSE frame may have been
388 sent but the connection closure process has not yet completed.
401 For QUIC connection SSL objects, this means that the connection closure process