lucaslorentz/caddy-docker-proxy works like Traefik, in that Container metadata labels are added to the reverse proxy configuration which is reloaded upon container events, which you can listen to when you subscribe to a Docker/Podman_v3 socket (which is unfortunately not read only)

So, with Caddy or Traefik, a container label can enable HTTP/3 (QUIC (UDP port 1704)) for just that container.

"Labels to Caddyfile conversion" https://github.com/lucaslorentz/caddy-docker-proxy#labels-to...

From https://news.ycombinator.com/item?id=26127879 re: containersec :

> > - [docker-socket-proxy] Creates a HAproxy container that proxies limited access to the [docker] socket

francislavoie

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

That 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/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

Yes, the docs have been updated at 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.