HTTP/3 and QUIC
What you'll learn: How HTTP/3 leverages the QUIC protocol built on UDP to overcome performance limitations of earlier HTTP versions.
The Problem with TCP-Based HTTP
HTTP/1.1 and HTTP/2 both run over TCP, which you learned provides reliable, ordered delivery. However, TCP has a limitation called head-of-line blocking: if one packet is lost, all subsequent packets must wait for retransmission, even if they belong to completely independent streams. This is especially problematic on unreliable networks (like mobile connections).
What is QUIC?
QUIC (Quick UDP Internet Connections) is a transport protocol that runs on top of UDP instead of TCP. Remember that UDP is connectionless and lightweight, with minimal guarantees. QUIC builds reliability, congestion control, and encryption directly into itself—essentially reimagining what TCP does, but designed from scratch for modern web needs.
Think of it like this: TCP is a single-lane highway where one stalled car blocks everyone behind it. QUIC is a multi-lane highway where each lane (stream) can proceed independently if another lane has a problem.
HTTP/3: HTTP Over QUIC
HTTP/3 is simply HTTP running on top of QUIC instead of TCP. Key advantages:
- No head-of-line blocking: Multiple streams are truly independent at the transport layer
- Faster connection establishment: QUIC combines the handshake and encryption setup (like HTTPS does with TLS) into a single round-trip, or even zero round-trips for repeat connections
- Better handling of network changes: Switching from Wi-Fi to mobile data doesn't break the connection because QUIC uses connection IDs instead of IP addresses
Because QUIC is built on UDP, it bypasses decades of TCP optimizations baked into network hardware, but gains flexibility and modern design advantages.
Key Takeaway: HTTP/3 uses QUIC over UDP to eliminate head-of-line blocking and reduce latency, offering independent stream multiplexing and faster connection setup compared to TCP-based HTTP/2.