HTTP/3: why and where are we?

on YouTube ↗37m

" summary

HTTP/3 runs over QUIC on UDP, replaces TCP+TLS with a single encrypted transport and gives independent streams to avoid TCP head‑of‑line blocking. Deployment is nontrivial: browsers and CDNs support it but traffic sits around 27% of requests, DNS HTTPS records (RFC 90460) help first‑try use. Implementations include nghttp3, quiche and MS QUIC; OpenSSL lacks the needed QUIC API, servers see roughly 3× CPU cost today and UDP blocking/fallbacks remain the main operational pain.

AI-written summary · about

" chapters (12)

1. 0:00HTTP/3 introduction
2. 3:16HTTP/1.1 limitations
3. 6:03HTTP/2 head-of-line blocking
4. 8:32Protocol evolution
5. 11:49Why QUIC and HTTP/3
6. 14:18QUIC replaces TCP/TLS
7. 17:51HTTP/3 benefits
8. 20:59Adopting HTTP/3
9. 25:40HTTP/3 deployment challenges
10. 30:39HTTP/3 adoption status
11. 33:15HTTP/3 in curl/libraries
12. 36:09Summary and future

" related talks

• 51mHTTP/3 and QUIC: Who, what, where, when and, WHY?Robin Marx · Devoxx Belgium 2024
• 34mHTTP/3 is comingDaniel Stenberg · JAX 2019
• 46mHTTP/3: It's all about the transport!Benoit Jacquemont · Dutch PHP Conference 2019
• 30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?Daniel Stenberg · GOTOpia November 2020
• 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