Why HTTP/3 and QUIC Are Revolutionizing Web Performance

HTTP History

1991 HTTP/1.1

2009 Google designed SPDY over TCP

2013 QUIC

2015 HTTP/2

2018 HTTP/3

HTTP/3 builds on QUIC, using UDP for high speed while preserving TLS security.

QUIC Overview

QUIC (Quick UDP Internet Connections) is a UDP‑based protocol that combines the benefits of TCP, TLS, and HTTP/2 with optimizations. It serves as the transport layer for HTTP/3.

Connection Establishment (RTT)

RTT (round‑trip time) measures only the request‑response travel time. HTTP/2 requires 3 RTT for a new connection (2 RTT with TLS 1.3 session resumption). HTTP/3 needs only 1 RTT for the first connection and 0 RTT for subsequent ones.

QUIC Handshake Steps

Client sends Inchoate Client Hello to request a connection.

Server generates g, p, a, computes A, and sends them in a Server Config with a Rejection message.

Client receives g, p, A, generates b, computes B and the initial key K, encrypts HTTP data with K, and sends B and encrypted data.

Server receives B, derives the same key, decrypts the data, updates its random number a and public key, sends a new Server Hello with the new key and HTTP response.

Connection Migration

TCP connections depend on a four‑tuple (source IP, source port, destination IP, destination port); any change forces a new connection, causing delays. QUIC uses a 64‑bit Connection ID, so connections survive IP or port changes.

Head‑of‑Line Blocking and Multiplexing

Both HTTP/1.1 and HTTP/2 suffer head‑of‑line (HoL) blocking at the TCP level. HTTP/2 introduces multiplexing to avoid HoL at the request level, but TCP’s HoL still affects it. QUIC eliminates HoL by using independent packets, allowing streams to proceed independently.

Congestion Control

QUIC adopts TCP‑like congestion control (Cubic) with improvements such as hot‑plugging new algorithms at the application layer, forward error correction (FEC) to recover lost packets, and dynamic algorithm selection based on network conditions.

Additional QUIC Features

Hot‑plugging congestion control algorithms.

Forward Error Correction (FEC) to reconstruct lost packets.

Monotonically increasing Packet Numbers to avoid ACK ambiguity.

ACK Delay accounting for more accurate RTT.

Support for up to 256 ACK blocks, reducing retransmissions.

Flow Control

QUIC implements flow control at both the connection and stream levels. The receiver advertises a receive window; when the window falls below half of the maximum, it sends a WINDOW_UPDATE to allow more data.

Overall, QUIC addresses many limitations of TCP‑based HTTP/2, offering lower latency, better resilience to network changes, and more efficient congestion and flow control.