HTTP/3 over QUIC reduces latency and improves multiplexing. Support is growing in browsers and CDNs. Ensure your stack (load balancer, app server) supports QUIC or is behind a QUIC-capable edge.
What QUIC and HTTP/3 are
- QUIC: Transport protocol (over UDP) that provides encryption (TLS 1.3), multiplexing, and connection migration. Replaces TCP+TLS for HTTP/3. First connection is faster (0-RTT or 1-RTT handshake) and head-of-line blocking is per stream, not per connection.
- HTTP/3: Same semantics as HTTP/2 (methods, headers, etc.) but over QUIC instead of TCP. Browsers and clients are increasingly using it when the server advertises support.
- Benefits: Lower latency on first request (especially on high-RTT links); better behavior under packet loss (one stream does not block others). Good for mobile and long-distance users.
Where support is
- Browsers: Chrome, Firefox, Safari, Edge support HTTP/3 (often enabled by default when server supports it). Fallback to HTTP/2 or HTTP/1.1 if not.
- CDNs: Many CDNs (Cloudflare, Fastly, etc.) support QUIC/HTTP/3 at the edge. You enable it in the CDN; traffic from client to CDN uses HTTP/3; CDN to origin can stay HTTP/1.1 or HTTP/2. Easiest way to get HTTP/3 without changing your origin stack.
- Origin: Your load balancer or app server may need to support QUIC (e.g. NGINX with QUIC module, Caddy, or cloud LB with HTTP/3). If you are behind a QUIC-capable CDN, origin can remain HTTP/1.1 or HTTP/2; the CDN terminates QUIC.
What to do
- Behind CDN: Enable HTTP/3 (or QUIC) in your CDN dashboard. No origin change needed if CDN terminates. Test with browser dev tools or
curl --http3(if supported). - Origin QUIC: If you want QUIC to the origin (e.g. no CDN or CDN passes through), install and configure a stack that supports QUIC. Use a recent version (QUIC is still evolving). Open UDP port (typically 443 same as HTTPS). Monitor for compatibility and performance.
- Fallback: Clients that do not support HTTP/3 will use HTTP/2 or HTTP/1.1. Ensure your server or CDN serves both. No need to force HTTP/3 only.
Summary
HTTP/3 over QUIC reduces latency and improves multiplexing. Support is growing in browsers and CDNs. Ensure your stack supports QUIC or is behind a QUIC-capable edge (e.g. CDN). Easiest path is often enable at CDN.
