HTTP/3 is coming

on YouTube ↗34m

" summary

HTTP/3 runs HTTP over QUIC (UDP with TLS built in) to fix TCP head‑of‑line blocking by giving each request its own independent stream and enabling 0‑RTT early data and faster handshakes. Clients discover it via the Alt‑Svc header. Deployments currently see ~3–7% QUIC failures because UDP is blocked or rate‑limited, servers pay ~2–3× CPU today, and Linux UDP stacks plus TLS APIs still require new tooling and library work.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 0:51Who is involved
3. 1:55TCP
4. 2:58HTTP
5. 12:22Quick
6. 12:39Google Quick
7. 20:15What is HTTP3
8. 25:12HTTP HTTPS
9. 26:52UDP
10. 28:27CPU intensive
11. 29:47TLS layer
12. 30:42Release date
13. 31:42Conclusion

" related talks

• 37mHTTP/3: why and where are we?Daniel Stenberg · Øredev 2023
• 30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?Daniel Stenberg · GOTOpia November 2020
• 51mHTTP/3 and QUIC: Who, what, where, when and, WHY?Robin Marx · Devoxx Belgium 2024
• 46mHTTP/3: It's all about the transport!Benoit Jacquemont · Dutch PHP Conference 2019
• 40mHTTP/3 - HTTP over QUIC is the next generationDaniel Stenberg · Full Stack Fest 2019
• 35mOn QUIC, HTTP/3 and tech stack unificationGabriel Michael Homa · DevConf.CZ 2026
• 34mSecuring the Next Version of HTTP: How QUIC and HTTP/3 Compare to HTTP/2NICK HARPER · Black Hat Asia 2020
• 34mQUIC and HTTP/3: Too Big to Fail?!Robin Marx · DrupalCon Amsterdam 2019