HTTP/3 where are we now? State of the art in our servers.
summary
Traffic Server already supports HTTP/3 and runs a working demo while httpd and Tomcat still need QUIC/TLS library work and extra engineering. Browsers advertise H3 then use an Alt-Svc upgrade; if UDP is blocked or responses glitch the browser falls back to H2/H1. Deployments require QUIC over UDP, and currently BoringSSL or patched OpenSSL for server stacks. Expect Traffic Server ready; httpd/Tomcat need more integration and testing.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 1:57HTTP/2 origins and features
- 7:29Why HTTP/3 was developed
- 11:10HTTP/3 basics and QUIC transport
- 16:12Server-side challenges with HTTP/3
- 20:15Demo setup and Alternate Service
- 23:35Testing and client implementations
- 27:37Current state and future outlook
related talks
45mHTTP/2, HTTP/3, and TLS State of the Art in our Servers
34mHTTP/3 is coming
37mHTTP/3: why and where are we?
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
46mHTTP/3: It's all about the transport!
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
40mHTTP/3 - HTTP over QUIC is the next generation
35mOn QUIC, HTTP/3 and tech stack unification