3 ms·
The point of the link in OP is that now in v2.6, Caddy enables HTTP/3 by default, and doesn't need to be explicitly enabled by the user. So I'm not exactly sur
by francislavoie 4y ago
The point of the link in OP is that now in v2.6, Caddy enables HTTP/3 by default, and doesn't need to be explicitly enabled by the user.
So I'm not exactly sure the point you're trying to make. But yes, CDP is an awesome project!
- westurner 4y agoThat is a good point. Is there any way to disable HTTP/3 support with just config? The (unversioned?) docs have: https://caddyserver.com/docs/modules/http#servers/experimental_http3 https://caddyserver.com/docs/modules/http#servers/experiment... : > servers/experimental_http3: Enable experimental HTTP/3 support. Note that HTTP/3 is not a finished standard and has extremely limited client support. This field is not subject to compatibility promises TIL caddy has Prometheus metrics support (in addition to automatic LetsEncrypt X.509 Cert renewals)
- mholt 4y agoYes, the docs have been updated at https://github.com/caddyserver/website https://github.com/caddyserver/website but haven't been deployed yet. There is a new protocols option: protocols h1 h2 will disable Http/3 but leave 1.1 and 2 on.
- francislavoie 4y agoYeah those docs are for v2.5. The experimental_http3 option is removed in v2.6 (which is currently only in beta, stable release coming soon). To configure protocols and disable HTTP/3, you'll now use the "protocols" option (inside of the "servers" global option), and it would look like "protocols h1 h2" (the default is "h1 h2 h3").