A lot of servers still don't support that.
Go http webserver doesn't support http 3 without external libraries. Nginx doesn't support http 3. Apache doesn't support http 3. node.js doesn't support http 3. Kubernetes ingress doesn't support http 3.
should I go on?
edit: even curl itself - which created the original document linked above - has http 3 just in an experimental build.
>Nginx doesn't support http 3
nginx do support it.
https://nginx.org/en/docs/quic.html
And I see I was not that wrong; the module is still marked as "experimental" and not built by default.
https://nginx.org/en/docs/http/ngx_http_v3_module.html
ah okay i was wrong there, mea culpa
The guy's point still stands - lots of popular software do not yet support http3.
> edit: even curl itself - which created the original document linked above - has http 3 just in an experimental build.
It's not experimental when built with ngtcp2, which is what you will get on distros like Debian 13-backports (plain Debian 13 uses OpenSSL-QUIC), Debian 14 and onward, Arch Linux and Gentoo.
Reference: https://curl.se/docs/http3.html
Well this statement have to be precised.
caddyserver v2 supports HTTP/3 and it's an webserver written in go https://caddyserver.com/features
FYI: There is also an rust webserver which supports HTTP/3. https://v2.ferronweb.org/
Go built-in webserver.