Deploying and Debugging HTTP/3
summary
Explains concrete failure modes: TLS session-resumption tokens cause a contagion that forces Google to disable QUIC after 10% of fleet fails; connection coalescing sends H3 requests where firewalls expect H2 and returns 403s; DNS + alt‑svc caching inflates H3 win to ~50% versus the true ~33% improvement; UDP amplification and the 3x amplification limit push some servers from 1RTT to 2RTT. Shows debugging with curl, Wireshark and qlog/qvis and notes qlog support in ~70% of QUIC implementations.
AI-written summary · about
chapters (7)
- 0:00The contagion bug
- 5:53HTTP/3 connection issues
- 9:59Performance metrics pitfalls
- 15:47Observability tools for QUIC
- 24:18UDP amplification in QUIC
- 31:53Challenges in H3 deployment
- 41:03Conclusion and final thoughts
related talks
40mHTTP/3 - HTTP over QUIC is the next generation
34mQUIC and HTTP/3: Too Big to Fail?!
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
35mOn QUIC, HTTP/3 and tech stack unification
37mHTTP/3: why and where are we?
34mHTTP/3 is coming
54mQUIC illustrated
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?