Lines Matching refs:not
32 to SSL_shutdown() when not being used with QUIC.
40 shutdown process and return 0 to indicate that the shutdown process has not yet
45 SSL_shutdown() should not be called if a previous fatal error has occurred on a
84 SSL_shutdown() does not affect an underlying network connection such as a TCP
98 not call SSL_shutdown() in this case, a close_notify alert will not be sent and
99 the behaviour will not be fully standards compliant.
110 If the underlying BIO is nonblocking and the shutdown process is not yet
111 complete (for example, because a close_notify alert message has not yet been
129 If this approach is not used, the second call to SSL_shutdown() (to complete the
131 it is called when the application has not read all pending application data
146 if the application does not wish to wait for the peer.
149 that the peer will not send more data, otherwise there is a risk of an
169 close_notify alert was successful or not. This makes the SSL session eligible
180 This is not standards-compliant behaviour. It should only be done when the
196 does not receive cryptographic protection, and therefore renders an application
212 Therefore, client applications which only write and do not read but which wish
237 not provided, an error code of 0 is used by default.
243 will not validate the string. If a reason is not provided, or SSL_shutdown() is
245 is copied and stored inside the QUIC connection SSL object and need not remain
250 Reason strings are intended for human diagnostic purposes only, and should not
259 These functions do not affect an underlying network BIO or the resource it
269 could not yet be transmitted, or which was sent but lost in the network, may not
274 whether during connection usage or during shutdown. If an application is not
296 SSL_shutdown_ex(); in this case, data remaining in stream send buffers may not
333 by sending a single QUIC packet. If that QUIC packet is lost, the peer will not
337 This will generally return 0 on success, indicating that the connection has not
382 The shutdown process is ongoing and has not yet completed.
385 peer has not yet replied in turn with its own close_notify.
388 sent but the connection closure process has not yet completed.
390 Unlike most other functions, returning 0 does not indicate an error.
391 L<SSL_get_error(3)> should not be called; it may misleadingly indicate an error
406 The shutdown was not successful.
411 It can also occur when not all data was read using SSL_read(), or if called
434 Licensed under the Apache License 2.0 (the "License"). You may not use
