Protocols
Saved & recent

HTTP/3

Also called: HTTP 3, h3

HTTP/3 maps HTTP exchanges onto QUIC rather than TCP. QUIC runs over UDP and provides reliable streams with integrated security. An HTTP request and its response share a bidirectional QUIC stream; separate streams can make progress without waiting for each other’s missing stream data.

If one image loses a packet, an unrelated stylesheet stream need not wait for that image’s retransmission as it would behind TCP’s single ordered byte stream. Loss still consumes time and can affect shared congestion control or application dependencies. HTTP/3 retains familiar HTTP meanings; it does not make requests unreliable merely because UDP carries QUIC packets.

Read first
HTTP, QUIC
Related
QUIC, HTTP/2, HTTPS, WebTransport
Further reading
IETF RFC 9114 — HTTP/3
QUIC · shared congestion control image stream image 1 image 3 image waits QUIC retransmits missing data stylesheet stream CSS 1 CSS 2 CSS can progress common UDP transport
A gap delays the affected QUIC stream, while another stream can deliver available data. QUIC supplies reliability above UDP; the streams still share connection and congestion constraints. Timing is schematic.

View in the full Protocols collection