| /doc/man3/ |
| A D | SSL_CTX_set_timeout.pod | 16 SSL_CTX_set_timeout() sets the timeout for newly created sessions for 17 B<ctx> to B<t>. The timeout value B<t> must be given in seconds. 19 SSL_CTX_get_timeout() returns the currently set timeout value for B<ctx>. 25 timeout value valid at this time. If the actual time is later than creation 26 time plus timeout, the session is not reused. 29 valid at the time of the session negotiation. Changes of the timeout value 40 The default value for session timeout is decided on a per protocol 42 All currently supported protocols have the same default timeout value 46 tickets. It is also used as the timeout value within the ticket itself. 57 SSL_CTX_set_timeout() returns the previously set timeout value. [all …]
|
| A D | BIO_socket_wait.pod | 18 int BIO_do_connect_retry(BIO *bio, int timeout, int nap_milliseconds); 24 It succeeds immediately if B<max_time> == 0 (which means no timeout given). 29 It succeeds immediately if B<max_time> == 0 (which means no timeout given). 36 i.e., connection succeeded, timeout has been reached, or an error occurred. 40 If the B<timeout> parameter is > 0 this indicates the maximum number of seconds 42 A value of 0 enables waiting indefinitely (i.e, no timeout), 49 return -1 on error, 0 on timeout, and 1 on success.
|
| A D | SSL_get_default_timeout.pod | 5 SSL_get_default_timeout - get default session timeout value 15 SSL_get_default_timeout() returns the default timeout value assigned to 20 Whenever a new session is negotiated, it is assigned a timeout value, 21 after which it will not be accepted for session reuse. If the timeout 24 timeout for the protocol will be used.
|
| A D | DTLS_set_timer_cb.pod | 20 timeout interval on the DTLS protocol. The callback function will be 23 The callback should return the timeout interval in micro seconds. 25 The I<timer_us> parameter of the callback is the last set timeout 29 At the beginning of the connection, if no timeout callback has been 30 set via DTLS_set_timer_cb(), the default timeout value is 1 second.
|
| A D | DTLSv1_handle_timeout.pod | 5 DTLSv1_handle_timeout - handle a pending timeout event for a DTLS or QUIC SSL 16 DTLSv1_handle_timeout() handles any timeout events which have become pending 30 Returns 1 if there was a pending timeout event and it was handled successfully. 32 Returns 0 if there was no pending timeout event, or if the SSL object is not a 35 Returns -1 if there was a pending timeout event but it could not be handled
|
| A D | X509_load_http.pod | 15 X509 *X509_load_http(const char *url, BIO *bio, BIO *rbio, int timeout); 16 X509_CRL *X509_CRL_load_http(const char *url, BIO *bio, BIO *rbio, int timeout); 39 If the B<timeout> parameter is > 0 this indicates the maximum number of seconds 42 while a value < 0 immediately leads to a timeout condition. 45 that have the same effect as the functions above but with infinite timeout 51 Error conditions include connection/transfer timeout, parse errors, etc.
|
| A D | SSL_SESSION_get_time.pod | 8 - retrieve and manipulate session time and timeout settings 41 SSL_SESSION_get_timeout() returns the timeout value set for session B<s> 44 SSL_SESSION_set_timeout() sets the timeout value for session B<s> in seconds 57 Sessions are expired by examining the creation time and the timeout value. 59 default timeout value at creation, respectively, as set by
|
| A D | DTLSv1_get_timeout.pod | 6 timeout event to be handled 23 function succeeds, returning 1. If no timeout is currently active, this function 32 Once the timeout expires, DTLSv1_handle_timeout() should be called to handle any 43 Returns 0 on failure, or if no timeout is currently active.
|
| A D | SSL_handle_events.pod | 18 timeout events which have become due, or may attempt, to the extent currently 34 Using SSL_handle_events() on an SSL object being used with a DTLS method allows timeout 49 timeout events to be handled properly, as well as incoming network data to be 57 periodically to allow timeout events to be handled. An application can find out
|
| A D | SSL_poll.pod | 70 const struct timeval *timeout, 127 The I<timeout> argument specifies the timeout to use, and, implicitly, whether 134 If I<timeout> is NULL, the function blocks indefinitely until at least one 139 If I<timeout> is non-NULL, and it points to a B<struct timeval> which is set to 145 If I<timeout> is non-NULL, and it points to a B<struct timeval> which is set to 164 If this flag is used in nonblocking mode (with a timeout of zero), no internal 167 If this flag is used in blocking mode (for example, with I<timeout> set to 412 would fail if called with a NULL I<timeout> parameter or a I<timeout> parameter
|
| A D | OSSL_HTTP_transfer.pod | 28 int timeout, BIO *bio_err, const char *prog); 33 size_t max_resp_len, int timeout, int keep_alive); 40 size_t max_resp_len, int timeout); 50 size_t max_resp_len, int timeout, int keep_alive); 152 A value <= 0 enables waiting indefinitely, i.e., no timeout. 161 If the I<timeout> parameter is > 0 this indicates the maximum number of 163 A value <= 0 enables waiting indefinitely, i.e., no timeout. 183 For the meaning of the I<expected_content_type>, I<expect_asn1>, I<timeout>, 259 Failure conditions include connection/transfer timeout, parse errors, etc.
|
| A D | OSSL_HTTP_REQ_CTX.pod | 39 int timeout, int keep_alive); 120 If the I<timeout> parameter is > 0 this indicates the maximum number of seconds 123 I<timeout> == 0 enables waiting indefinitely, i.e., no timeout can occur. 125 I<timeout> < 0 takes over any value set via the I<overall_timeout> argument of 126 L<OSSL_HTTP_open(3)> with the default being 0, which means no timeout. 155 the response body, the HTTP transfer timeout, and "keep-alive" are treated. 170 in order to exchange a request and response or until a timeout is reached.
|
| A D | SSL_get_event_timeout.pod | 51 L<DTLSv1_get_timeout(3)> in that the case where no timeout is active is 57 Once the timeout expires, L<SSL_handle_events(3)> should be called to handle any
|
| A D | SSL_get_conn_close_info.pod | 118 idle timeout occurs). 149 The connection was terminated immediately due to the idle timeout expiring.
|
| A D | SSL_get_value_uint.pod | 163 Negotiated feature value. This configures the desired QUIC idle timeout in 164 milliseconds, where 0 represents a lack of an idle timeout. This feature can 231 incoming datagrams and timeout events are processed. 239 generated, and pending timeout events are not processed. This allows an
|
| A D | BIO_f_ssl.pod | 71 BIO_set_ssl_renegotiate_timeout() sets the renegotiate timeout of SSL BIO B<b> 73 When the renegotiate timeout elapses the session is automatically renegotiated. 76 renegotiations due to I/O or timeout of SSL BIO B<b>.
|
| A D | BIO_s_datagram.pod | 161 call to L<BIO_read(3)>) may have been caused by a receive timeout. 166 call to L<BIO_write(3)>) may have been caused by a send timeout. 222 the receive timeout for the socket for the purposes of future L<BIO_read(3)>
|
| /doc/designs/ddd/ |
| A D | ddd-02-conn-nonblocking.c | 321 struct timeval timeout; in main() local 323 int timeout = 2000 /* ms */; in main() local 329 ms_to_timeval(&timeout, 2000); in main() 369 if (t.tv_sec < 0 || timercmp(&t, &timeout, >)) in main() 370 t = timeout; in main() 373 timeradd(&start, &timeout, &deadline); in main() 381 if (poll(&pfd, 1, timeout) == 0) in main() 413 if (t.tv_sec < 0 || timercmp(&t, &timeout, >)) in main() 414 t = timeout; in main() 417 timeradd(&start, &timeout, &deadline); in main() [all …]
|
| A D | ddd-04-fd-nonblocking.c | 302 struct timeval timeout; in main() local 304 int timeout = 2000 /* ms */; in main() local 311 ms_to_timeval(&timeout, 2000); in main() 384 if (t.tv_sec < 0 || timercmp(&t, &timeout, >)) in main() 385 t = timeout; in main() 388 timeradd(&start, &timeout, &deadline); in main() 396 if (poll(&pfd, 1, timeout) == 0) in main() 428 if (t.tv_sec < 0 || timercmp(&t, &timeout, >)) in main() 429 t = timeout; in main() 432 timeradd(&start, &timeout, &deadline); in main() [all …]
|
| A D | ddd-05-mem-nonblocking.c | 297 static int pump(APP_CONN *conn, int fd, int events, int timeout) argument 314 if (poll(&pfd, 1, timeout) == 0) 360 int timeout = 2000 /* ms */; local 428 if (pump(conn, fd, get_conn_pending_tx(conn), timeout) != 1) { 443 if (pump(conn, fd, get_conn_pending_rx(conn), timeout) != 1) {
|
| A D | ddd-02-conn-nonblocking-threads.c | 265 int timeout = 2000 /* ms */; in main() local 302 if (poll(&pfd, 1, timeout) == 0) { in main() 320 if (poll(&pfd, 1, timeout) == 0) { in main()
|
| /doc/designs/quic-design/server/ |
| A D | quic-polling.md | 175 timeout using `SSL_get_event_timeout`. 416 **Q. What happens in the event of idle timeout?** 817 * after the specified timeout, or immediately with failure if no timeout 865 const struct timeval *timeout, 1013 * timeout outcome. 1262 struct timeval timeout = { 0 }; 2025 /* The timeout concerns reads. */ 2027 /* The timeout concerns writes. */ 2029 /* The timeout concetns accepts. */ 2033 /* The timeout concerns connects. */ [all …]
|
| /doc/designs/quic-design/ |
| A D | connection-state-machine.md | 63 timeout. 177 - the Terminated state if the idle timeout expires; a `CONNECTION_CLOSE` 200 The endpoint progresses to the Terminated state after a timeout 205 to the timeout expiring. This indicates that the peer is also 214 The endpoint progresses to the Terminated state after a timeout 219 idle timeout, stateless reset), a connection always ultimately ends up in this 447 `CAN_SEND` is expected to be raised due to a timeout prescribed by the 459 - `IDLE_TIMEOUT` is raised after the connection idle timeout expires.
|
| /doc/man7/ |
| A D | ossl-guide-quic-client-non-block.pod | 69 for the state of the underlying socket to change or until a timeout expires 114 * a GUI every 100ms. One way to do that would be to use the timeout in 118 * because of the timeout. If the 100ms GUI timeout has expired but the 119 * tvp timeout has not then go and update the GUI and then restart the 162 socket(s) to become readable/writeable or until the timeout has expired before
|
| A D | ossl-guide-tls-client-non-block.pod | 112 * a GUI every 100ms. One way to do that would be to add a 100ms timeout 115 * because of the timeout. If it is due to the timeout then update the 128 supports a "timeout" (as do most other similar functions) so in your own 130 while waiting for the socket state to change. But we don't use that timeout
|