Lines Matching full:connection

64 SSL_shutdown, SSL_shutdown_ex \- shut down a TLS/SSL or QUIC connection
83 \&\fBSSL_shutdown()\fR shuts down an active connection represented by an SSL object. \fIssl\fR \fBM…
105 connection; i.e., if \fBSSL_get_error\fR\|(3) has returned \fBSSL_ERROR_SYSCALL\fR or
117 These steps can occur in either order depending on whether the connection
126 Calling \fBSSL_shutdown()\fR only closes the write direction of the connection; the
129 until the peer decides to close the connection in turn. The peer might
133 \&\fBSSL_shutdown()\fR does not affect an underlying network connection such as a TCP
134 connection, which remains open.
190 (such that it returns 0) and then close the underlying connection without
199 connection.
204 peer of connection shutdown.
207 the underlying connection (e.g. a TCP connection) for further communication; in
219 \&\fBSSL_shutdown()\fR can be modified to set the connection to the "shutdown"
231 alert message but simply close the underlying transport (e.g. a TCP connection)
249 If a client application only writes to an SSL/TLS or DTLS connection and never
261 When used with a QUIC connection SSL object, \fBSSL_shutdown()\fR initiates a QUIC
269 provide additional information to the peer on the reason why a connection is
282 is copied and stored inside the QUIC connection SSL object and need not remain
291 \&\fBSSL_shutdown_ex()\fR (or \fBSSL_shutdown()\fR) for a given QUIC connection SSL object.
295 represents; for example, a UDP datagram provided to a QUIC connection as the
300 TLS/TCP connection, where reliable transmission of buffered data is the
302 QUIC connection SSL object or exits before completing the shutdown process using
309 whether during connection usage or during shutdown. If an application is not
336 Aspects of how QUIC handles connection closure must be taken into account by
337 applications. Ordinarily, QUIC expects a connection to continue to be serviced
339 to ensure that any connection closure notification sent to the peer was
341 RFC-compliant QUIC connection closure process could take of the order of
346 As such, there are two shutdown modes available to users of QUIC connection SSL
357 indicating the closure process is complete and the connection is now fully shut
361 In this mode, the peer is notified of connection closure on a best effort basis
363 know that the connection has terminated until the negotiated idle timeout (if
366 This will generally return 0 on success, indicating that the connection has not
381 waits until the peer initiates a shutdown or the connection otherwise becomes
385 If a locally initiated shutdown has already been triggered or the connection has
389 stream data cannot be flushed after a peer closes the connection. Stream data
391 the connection, though there is no guarantee of this.
394 \&\fBSSL_shutdown()\fR and \fBSSL_shutdown_ex()\fR block if the connection is configured in
407 For QUIC connection SSL objects, a CONNECTION_CLOSE frame may have been
408 sent but the connection closure process has not yet completed.
420 For QUIC connection SSL objects, this means that the connection closure process