Lines Matching refs:shutdown
35 exact nature of how a shutdown is performed depends on the underlying protocol
40 shutdown process and return 0 to indicate that the shutdown process has not yet
41 completed. Once the shutdown process has completed, subsequent calls to
52 close_notify alert message. The shutdown process for SSL/TLS and DTLS
59 A close_notify shutdown alert message is sent to the peer.
63 A close_notify shutdown alert message is received from the peer.
68 shutdown process was first initiated by the local application or by the peer.
72 Calling SSL_shutdown() on an SSL/TLS or DTLS SSL object initiates the shutdown
73 process and causes OpenSSL to try to send a close_notify shutdown alert to the
74 peer. The shutdown process will then be considered completed once the peer
75 responds in turn with a close_notify shutdown alert message.
82 application's shutdown indication.
89 If the peer was the first to initiate the shutdown process by sending a
94 prior to initiating the shutdown has been read. An application should handle
96 turn, completing the shutdown process, though it may choose to write additional
103 Regardless of whether a shutdown was initiated locally or by the peer, if the
107 peer (returning 1 and completing the shutdown process). Calls to SSL_shutdown()
110 If the underlying BIO is nonblocking and the shutdown process is not yet
114 shutdown process is still ongoing; in this case, a call to L<SSL_get_error(3)>
117 An application can then detect completion of the shutdown process by calling
118 SSL_shutdown() again repeatedly until it returns 1, indicating that the shutdown
122 However, the preferred method of waiting for the shutdown to complete is to use
130 shutdown by confirming receipt of the peer's close_notify message) will fail if
145 waiting for the peer's response. This allows for a more rapid shutdown process
148 This alternative "fast shutdown" approach should only be done if it is known
158 peer of connection shutdown.
160 The fast shutdown approach can only be used if there is no intention to reuse
162 this case, the full shutdown process must be performed to ensure
175 SSL_shutdown() can be modified to set the connection to the "shutdown"
177 L<SSL_CTX_set_quiet_shutdown(3)>. When "quiet shutdown" is enabled,
213 to benefit from session resumption are advised to perform a complete shutdown
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
275 using thread assisted mode, an application conducting shutdown should either
284 other words, the shutdown process waits until all data written by the
286 acknowledged by the peer. Only once this process is completed is the shutdown
294 This behaviour of flushing streams during the shutdown process can be skipped by
313 As such, there are two shutdown modes available to users of QUIC connection SSL
318 =item RFC compliant shutdown mode
320 This is the default behaviour. The shutdown process may take a period of time up
330 =item Rapid shutdown mode
343 If B<SSL_SHUTDOWN_FLAG_RAPID> is specified in I<flags>, a rapid shutdown is
344 performed, otherwise an RFC-compliant shutdown is performed.
347 application can subsequently change its mind about performing a rapid shutdown
352 In some cases, an application may wish to wait for a shutdown initiated by the
355 waits until the peer initiates a shutdown or the connection otherwise becomes
357 either success or failure depending on whether a shutdown has occurred.
359 If a locally initiated shutdown has already been triggered or the connection has
382 The shutdown process is ongoing and has not yet completed.
396 The shutdown was successfully completed.
406 The shutdown was not successful.
