public final Enum QuicTransportErrors

AEAD limit reached error

From RFC 9000, Section 20.1:

An endpoint has reached the confidentiality or integrity limit
for the AEAD algorithm used by the given connection.

Application error.

From RFC 9000, Section 20.1:

The application or application protocol caused the connection to be closed.

Connection id limit error.

From RFC 9000, Section 20.1:

The number of connection IDs provided by the peer exceeds
the advertised active_connection_id_limit.

Connection refused error.

From RFC 9000, Section 20.1:

The server refused to accept a new connection.

Crypto buffer exceeded error.

From RFC 9000, Section 20.1:

An endpoint has received more data in CRYPTO frames than it can buffer.

Crypto error.

From RFC 9000, Section 20.1:

The cryptographic handshake failed. A range of 256 values is
reserved for carrying error codes specific to the cryptographic
handshake that is used. Codes for errors occurring when
TLS is used for the cryptographic handshake are described
in Section 4.8 of [QUIC-TLS].

See Also

Section 4.8 of RFC 9001 [QUIC-TLS]

Final size error.

From RFC 9000, Section 20.1:

(1) An endpoint received a STREAM frame containing data that exceeded the previously
    established final size,
(2) an endpoint received a STREAM frame or a RESET_STREAM frame containing a final
    size that was lower than the size of stream data that was already received, or
(3) an endpoint received a STREAM frame or a RESET_STREAM frame containing a
    different final size to the one already established.

Flow control error.

From RFC 9000, Section 20.1:

An endpoint received more data than it permitted in its advertised data limits;
see Section 4.

Frame encoding error.

From RFC 9000, Section 20.1:

An endpoint received a frame that was badly formatted -- for instance,
a frame of an unknown type or an ACK frame that has more
acknowledgment ranges than the remainder of the packet could carry.

Internal Error.

From RFC 9000, Section 20.1:

The endpoint encountered an internal error and cannot
continue with the connection.

Invalid token error.

From RFC 9000, Section 20.1:

A server received a client Initial that contained an invalid Token field.

Key update error.

From RFC 9000, Section 20.1:

An endpoint detected errors in performing key updates; see Section 6 of [QUIC-TLS].

See Also

Section 6 of RFC 9001 [QUIC-TLS]

No error.

From RFC 9000, Section 20.1:

An endpoint uses this with CONNECTION_CLOSE to signal that
the connection is being closed abruptly in the absence
of any error.

No viable path error.

From RFC 9000, Section 20.1:

An endpoint has determined that the network path is incapable of
supporting QUIC. An endpoint is unlikely to receive a
CONNECTION_CLOSE frame carrying this code except when the
path does not support a large enough MTU.

Protocol violiation error.

From RFC 9000, Section 20.1:

An endpoint detected an error with protocol compliance that
was not covered by more specific error codes.

Stream limit error.

From RFC 9000, Section 20.1:

An endpoint received a frame for a stream identifier that exceeded its advertised
stream limit for the corresponding stream type.

Stream state error.

From RFC 9000, Section 20.1:

An endpoint received a frame for a stream that was not in a state that permitted
that frame; see Section 3.

See Also

Transport parameter error.

From RFC 9000, Section 20.1:

An endpoint received transport parameters that were badly
formatted, included an invalid value, omitted a mandatory
transport parameter, included a forbidden transport
parameter, or were otherwise in error.

Error negotiating version.

External Specification

https://www.rfc-editor.org/rfc/rfc9368#name-version-downgrade-preventio