QUIC and HTTP/3: Too Big to Fail?!
summary
QUIC encrypts transport headers and adds features like the spin bit and an amplification limit of three, but 3–5% of networks already drop UDP and some firewalls recommend blocking QUIC. TLS 1.3 resumption gives zero RTT on TCP too; TCP Fast Open narrows the gap. QUIC removes transport head‑of‑line blocking, yet implementations can hoard bandwidth (examples taking ~2/3 of link) and many CDNs (40 checked) misimplement HTTP/3 prioritization. Use quic‑go, Cloudflare’s nginx QUIC patch or Caddy and Chrome/Edge Canary with flags to experiment.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:47Why Do We Need Quick
- 10:52Tls 1 3 Connection Resumption
- 11:27Tcp Fast Open
- 13:03Replay Attack
- 16:40Your Congestion Control Algorithm
- 27:31Forward Error Correction
- 30:47Http Version Attribute to Drupal Cache
related talks
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
37mHTTP/3: why and where are we?
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
46mHTTP/3: It's all about the transport!
34mSecuring the Next Version of HTTP: How QUIC and HTTP/3 Compare to HTTP/2
40mHTTP/3 - HTTP over QUIC is the next generation
35mOn QUIC, HTTP/3 and tech stack unification
34mHTTP/3 is coming