Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to add HTTP3 flag (optional) #241

Closed
tkreindler opened this issue May 3, 2021 · 4 comments
Closed

Request to add HTTP3 flag (optional) #241

tkreindler opened this issue May 3, 2021 · 4 comments
Labels

Comments

@tkreindler
Copy link

With HTTP3 being supported on all browsers now and widely useful, it'd be nice to have an environment variable you can optionally pass to the container to add

{
experimental_http3
}

to the Caddyfile and enable http3.

@francislavoie
Copy link
Collaborator

francislavoie commented May 3, 2021

Just add global options as a label to your caddy-docker-proxy service. No need for anything extra.

caddy.servers.protocol.experimental_http3: ""

Be aware that the syntax for this global option is changed since v2.3.0, it's now nested within servers. See the docs:

https://caddyserver.com/docs/caddyfile/options

@seonglae
Copy link

Is global option by labels still available? I added http3 label to caddy service but protocol is still h2!

I'm using lucaslorentz/caddy-docker-proxy:2.4-alpine

@francislavoie
Copy link
Collaborator

Yes, see the README for how to configure global options.

Make sure you review the Global Options docs on the Caddy website for how to configure experimental_http3, it's nested a couple levels deeper.

@emilylange
Copy link

@seonglae

I added http3 label to caddy service but protocol is still h2!

The caddy-docker-proxy plugin leverages reloads, which seem to be broken with http/3 at the moment.
See caddyserver/caddy#4348 and caddyserver/caddy#4413 for more information :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants