HTTP/3 and QUIC: Who, what, where, when and, WHY?
summary
HTTP/3 runs over QUIC (on UDP), replaces TCP-like behavior by encrypts transport headers and deeply integrates TLS so future protocol changes avoid breaking middleboxes; it adds connection migration via connection IDs, supports 0‑RTT with a 3x amplification limit to reduce spoofing risk, and removes TCP head‑of‑line blocking by multiplexing streams at the transport. Measured gains vary: Wix reports up to 50% faster TTFB (practical deployments see ~30% on normal handshakes), CDNs just “flip a switch,” self‑hosting remains complex.
AI-written summary · about
chapters (8)
- 0:00Introduction to HTTP/3
- 3:20Limitations of TCP
- 8:37The design of QUIC
- 12:280-RTT security trade-offs
- 18:53Connection migration
- 29:10Removing head-of-line blocking
- 38:56Performance and implementation
- 47:48Conclusion and outlook
related talks
37mHTTP/3: why and where are we?
46mHTTP/3: It's all about the transport!
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
34mHTTP/3 is coming
40mHTTP/3 - HTTP over QUIC is the next generation
35mOn QUIC, HTTP/3 and tech stack unification
34mSecuring the Next Version of HTTP: How QUIC and HTTP/3 Compare to HTTP/2
34mQUIC and HTTP/3: Too Big to Fail?!