HTTP/3 replaces TCP with QUIC to cut connection latency
This article explains HTTP/3, the latest major revision of the HyperText Transfer Protocol, which replaces TCP with QUIC to eliminate head-of-line blocking and reduce connection setup latency. It details how HTTP/3 improves performance, especially on lossy networks, by utilizing QUIC's independent stream delivery, 0-RTT resumption, and connection migration capabilities. The article also covers the security aspects, adoption rates across browsers and CDNs, and configuration examples for various web servers.
Key Takeaways
- HTTP/3 uses QUIC, a UDP-based transport with built-in TLS 1.3, instead of TCP to avoid head-of-line blocking.
- A new QUIC connection needs 1 RTT, while 0-RTT resumption can send application data in the first packet.
- Cloudflare says about 21% of its requests use HTTP/3, versus 50% for HTTP/2 and 29% for HTTP/1.1.
- Google reported a 14% speed improvement for the slowest 10% of users; Fastly and Wix reported 18–33% lower time to first byte.
- HTTP/3 requires UDP port 443, and browsers can discover support through Alt-Svc headers or HTTPS DNS records.
Why It Matters
HTTP/3 mainly matters where streaming delivery is most sensitive to latency and packet loss: mobile networks, satellite links, and other constrained paths. The protocol keeps HTTP semantics intact while changing the transport to QUIC, so the ecosystem impact is mostly in server, CDN, and browser support rather than application rewrites. Adoption is already visible in major browsers and CDNs, with Cloudflare citing 21% of requests on HTTP/3. The next signal to watch is whether more traffic shifts through Alt-Svc and HTTPS DNS discovery as UDP 443 support becomes standard.
Read full article at http.dev