Mental model
HTTP/1.1 and HTTP/2 rely on TCP, where packet loss on a single stream stalls all multiplexed streams (TCP Head-of-Line Blocking). HTTP/3 replaces TCP with QUIC, a UDP-based transport protocol providing independent streams, integrated TLS 1.3 encryption, and 0-RTT handshakes.
HTTP/3 Client Request (UDP)
QUIC 0-RTT Handshake (TLS 1.3 built-in)
Independent Stream Framing over UDP
Zero TCP Head-of-Line Blocking
Connection Migration across IP Networks
Theory
- UDP Transport: Bypasses OS kernel TCP stack limitations, enabling per-stream packet loss recovery. Packet loss on Stream A does NOT block packet delivery on Stream B.
- Connection IDs: Identifies client connections via 64-bit Connection IDs rather than standard
IP:Port4-tuples. Allows mobile devices to switch networks (e.g. Wi-Fi to 5G) without dropping active HTTP/3 streams. - 0-RTT Handshake: Merges transport and TLS 1.3 cryptographic handshakes into a single round-trip, allowing clients to send HTTP requests on the very first packet.
bash(6 lines)
1# Verify HTTP/3 support on web edge server using cURL
2curl --http3 -I https://fullstackaihub.com
3
4# HTTP/3 Response Header indicating QUIC support
5# Alt-Svc: h3=":443"; ma=86400
Alternatives and trade-offs
- HTTP/2 over TCP: Fast stream multiplexing over a single socket; degrades on lossy networks (cellular/mobile) due to TCP head-of-line blocking.
- HTTP/3 over QUIC (UDP): Eliminates head-of-line blocking, 0-RTT reconnects, mobile connection migration; higher UDP CPU processing overhead on legacy router hardware.
Failure modes and misconceptions
- UDP Blocking Firewalls: Enterprise firewalls blocking UDP port 443 cause HTTP/3 connections to fail unless client fallback to HTTP/2 over TCP is configured (
Alt-Svcheader negotiation). - High CPU Memory Copies: Operating system kernels process UDP packets with higher per-packet CPU copy overhead than offloaded TCP. Use UDP sendmmsg/recvmmsg and GRO (Generic Receive Offload) kernel optimizations.
Reflect before revealing the guide
Decision scenario
Deploy HTTP/3 (QUIC) on public edge gateways with automatic HTTP/2 TCP fallback to maximize performance for mobile clients operating on lossy cellular networks.
Learning outcomes
- Contrast HTTP/2 over TCP with HTTP/3 over UDP-based QUIC.
- Explain QUIC 0-RTT handshakes and connection migration mechanics.
- Mitigate UDP blocking issues with
Alt-Svcheader fallbacks.
Trade-offs
HTTP/3 eliminates TCP head-of-line blocking and network migration delays, but requires UDP firewall pass-through and modern proxy support.