Lines Matching refs:not
87 APIs are not listed here; see [quic-api-ssl-funcs.md](./quic-api-ssl-funcs.md)
141 - **Never**: Does not interact with `SSL_get_error`.
153 SSL object. QUIC stream SSL objects do not allow these calls to be
157 inapplicable to QUIC, so it is not supported.
181 **Note:** Attempting to proceed in this state will not function for now because
182 we do not implement server support at this time. However, the semantics of this
251 other words, it blocks until it can buffer the data. This does not necessarily
321 If a QUIC stream SSL object is freed for a stream which has not reached a
334 any data which was appended to the stream via `SSL_write` may or may not have
335 already been transmitted, and even if already transmitted, may or may not be
341 connection SSL object is not freed and that the connection remains healthy.
348 not been shutdown properly is freed using this function:
350 - Any data which was pending transmission or retransmission will not be
353 - The connection closure process will not function correctly or in an
354 RFC-compliant manner. Connection closure will not be signalled to the peer
372 TLS, though not to DTLS).
399 Should not require any changes.
411 this mode does not take effect until the non-partial write operation is
449 This is similar to the existing `DTLSv1_get_timeout` function, but it is not
457 infinite timeout using a 0 return value, which does not allow a failure
503 should cause an application to call `SSL_handle_events`. These functions do not
519 write), not both. This call will not be implemented for QUIC (e.g. always
573 connection closure process is initiated if it has not already begun.
582 end-of-stream conditions) may not be transmitted to the peer. This flag may be
586 `SSL_stream_reset`) is not transmitted by this function.
602 `CONNECTION_CLOSE` frame sent is lost, the peer will not know that the
606 not yet reached the Terminating state (unless it has already done so, in which
610 sent but does not otherwise block. In non-blocking mode, this should be called
627 Calling `SSL_shutdown_ex` on a QUIC stream SSL object is not valid; such a call
632 `SSL_shutdown` and it is not desired for such calls to affect the whole
640 fails. These fields are ignored for SSL objects which do not represent QUIC
701 not affected.
704 the stream. It may not be called on an incoming unidirectional stream.
728 * The read or write part of the stream is still available and has not been
824 closed, or the respective part of the stream does not exist (e.g. for a
875 may or may not have an associated default stream. There may only be at most one
884 Initially these APIs will not be thread safe over the same connection, but in
905 This is not yet urgent but will be more relevant for concurrent server
937 * not also the QUIC connection object.
959 * does not have a default stream.
977 * or UINT64_MAX if the stream ID is not available. If called on a QUIC
1138 * stream SSL object, not the QUIC connection SSL object, as no default
1202 not preserved, therefore the BIO provided to libssl is, as provided, unusable
1203 for the purposes of implementing QUIC. Moreover, output buffering is not a
1210 - Require applications to be changed to not use QUIC with a `BIO_f_buffer`.
1253 not all OSes can provide support:
1255 - Iovecs (which have also been determined not to be necessary for a
1288 actual fact the opposite end of the `BIO_s_dgram_pair` does not.
1321 packets) varies by OS. Thus, it may not be available in all circumstances. A
1328 (`BIO_CTRL_DGRAM_SET_LOCAL_ADDR_ENABLE`). If local addressing support has not
1334 receiving packets and we do not wish to do this automatically inside the
1385 A BIO may not necessarily be able to provide a poll descriptor. For example,
1386 memory-based BIOs such as `BIO_s_dgram_pair` do not correspond to any OS
1388 `BIO_get_wpoll_descriptor` calls are not supported for such BIOs.
1391 not is known as non-pollable. `BIO_s_dgram` supports these functions.
1399 `BIO_s_dgram_pair`, it is unidirectional and does not support peer addressing or
1425 handshake has not yet been *confirmed*. Moreover, RFC 9001 s. 4.1.2 states:
1445 buffer the data. This does not necessarily mean that the data has actually been
1466 secretly keeping QUIC state around after a call to `SSL_free` does not seem
1488 allows immediate progression to the Draining state. However, a peer is *not*
1493 In the Draining state we simply ignore all incoming traffic and do not
1501 means to ensure that late-arriving packets do not induce a response, such as
1508 the draining state (the same may not be the case for the server role when
1517 and completes immediately. The Closing and Draining states are not used, and
1522 unlikely to be reliable and since this message is not authenticated, QUIC
1537 draining state is relevant. Since we conclude above that we do not need to
1564 If an ID has not been allocated to a stream, obviously incoming data cannot be
1565 addressed to it. However, supposing that an implementation does not do this,
1580 A peer is not generally notified of the creation of a stream which has not sent
1584 specific discussion of this possibility but does not preclude it. As such, in
1589 not yet sent any data via a zero-length stream frame, or
1613 bidirectional or unidirectional stream is being used; otherwise, we do not know
