NO_ERROR
QUIC NO_ERROR (0x00) is used in CONNECTION_CLOSE to signal a clean connection shutdown with no error condition. Unlike most error codes, NO_ERROR is not an error – it is the normal termination signal. A connection closed with NO_ERROR was operating correctly up to the point of closure.
Code
0x00
Decimal
0
Standard
RFC 9000 §20
Description
NO_ERROR is sent in CONNECTION_CLOSE frames when the endpoint wants to terminate the connection cleanly without any error condition. This is the QUIC equivalent of a clean TCP FIN. The peer should process any already-received data and then close the connection. NO_ERROR can be sent by either the client or server. Common scenarios: the HTTP/3 request and response completed successfully and the server is closing an idle connection, or the client finished its session and is shutting down. Distinguishing NO_ERROR from missing CONNECTION_CLOSE: a QUIC connection that simply stops receiving packets (network partition, crashed peer) does not generate any error code. NO_ERROR is an explicit clean close, not an absence of error.
Common Causes
- –Normal end-of-session clean connection shutdown
- –Idle connection timeout with no pending streams
- –Server gracefully closing connection after all HTTP/3 requests completed