Http3 #6558
Open
Http3 #6558
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch updates caddy and also creates the foundation to support http3. It does not change anything for existing installations, so I don't think there is any harm by merging this.
It changes the ports inside the proxy container to the http default ports (80 and 443 instead 8000 and 8001). But the docker-compose file still exposes the old port, so nothing should change.
This change is important. In my tests it was only possible to use http3 on the default ports. It seems, that the browsers currently do not accept http3 on other ports. Caddy sets the alt-svc header to its
https_port. This has to be 443.