HTTP/2, HTTP/3, and TLS State of the Art in our Servers
summary
Servers already enable HTTP/2 with TLS (OpenSSL 3.0 supported) and show a small CPU overhead from multiplexing; configuration is one connector or one line in httpd/trafficserver. HTTP/3 runs over QUIC over UDP and requires TLS 1.3 and alt‑svc negotiation; browsers (Chrome, Firefox) support h3 but pick versions differently. A working prototype uses Traffic Server to accept UDP h3 (draft‑29), proxy to Tomcat over HTTP/1.1, and demos show Chrome successfully using alt-svc with port and draft29.
AI-written summary · about
related talks
30mHTTP/3 where are we now? State of the art in our servers.
34mHTTP/3 is coming
37mHTTP/3: why and where are we?
46mHTTP/3: It's all about the transport!
40mHTTP/3 - HTTP over QUIC is the next generation
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
30mHTTP/3 Is Next Generation HTTP. Is It QUIC Enough?
01h 00mHTTP/2 - The future of the web today