HTTP/3
What is HTTP/3?
HTTP/3, defined in RFC 9114, is the first HTTP version to run over QUIC (RFC 9000) instead of TCP, so one lost packet only delays its own stream rather than stalling every multiplexed request. AdminKit's TLS certificate chain check validates the same chain concept that carries into the QUIC connection HTTP/3 runs on.
By AdminKit team, Netbase JSC · Updated
HTTP/3, defined in RFC 9114, is the third major version of HTTP, and the first to run over QUIC (defined in RFC 9000) instead of TCP. Earlier versions map HTTP semantics — methods, headers, status codes — onto a TCP connection; HTTP/2 multiplexes many requests over one TCP connection, but TCP’s own in-order delivery means a single lost packet stalls every multiplexed stream until it is retransmitted, even requests that packet had nothing to do with. HTTP/3 keeps HTTP/2’s multiplexing model but delegates it to QUIC, which recovers loss independently per stream, so one dropped packet only delays the stream it belonged to rather than every request sharing the connection — Cloudflare’s own explainer on HTTP/3 covers the same head-of-line-blocking fix. IANA’s QUIC registry tracks the transport parameters and frame types that make this per-stream recovery possible. A server and client negotiate HTTP/3 the same way they negotiate h2 versus http/1.1: through ALPN inside the TLS handshake QUIC already performs, using the protocol ID “h3”. A server already serving a client over HTTP/1.1 or HTTP/2 can also advertise HTTP/3 support using the Alt-Svc response header, letting that client upgrade to QUIC on a later request instead of requiring it on the very first connection. MDN’s Alt-Svc reference notes that this is how new protocol versions can be advertised without affecting in-flight requests. This is a different kind of multi-path behavior from Multipath TCP, which spreads one TCP connection across several network interfaces at once rather than multiplexing streams inside a single QUIC connection the way HTTP/3 does.
AdminKit groups hTTP/3 under its machine protocols cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
Why does HTTP/2 still suffer from head-of-line blocking if HTTP/3 doesn't?
HTTP/2 multiplexes many requests over one TCP connection, but TCP's own in-order delivery means a single lost packet stalls every multiplexed stream until it's retransmitted, even requests that packet had nothing to do with. HTTP/3 delegates multiplexing to QUIC instead, which recovers loss independently per stream.
How do a client and server agree to use HTTP/3?
The same way they negotiate h2 versus http/1.1: through ALPN inside the TLS handshake QUIC already performs, using the protocol ID "h3". A server can also advertise HTTP/3 support to an existing HTTP/1.1 or HTTP/2 client via the Alt-Svc response header, letting that client upgrade on a later request.
What transport does HTTP/3 run over?
QUIC (RFC 9000), which itself runs over UDP rather than TCP -- making HTTP/3 (RFC 9114) the first HTTP version not built on top of a TCP connection.
Is HTTP/3's multi-path behavior the same as Multipath TCP?
No -- they solve different problems. Multipath TCP spreads one TCP connection across several network interfaces at once, while HTTP/3 multiplexes many independent streams inside a single QUIC connection; neither mechanism does what the other does.