refactor(http3): use http3 instead of quic #11010
Merged
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.
Description
In #10989, I add
enable_quic
option toconfig-default.yaml
. Butenable_quic
does not match the mainstream gateway configuration. Both Cloudflare and AWS useenable_http3
. So I want to changeenable_quic
toenable_http3
.For enable
HTTP/3
in nginx, we have two steps to do.quic
in alisten
directive for one port.TLS v1.3
http3
directive inserver
/http
directiveeg.
Here I give two examples
config-defaul.yaml
exmaple 1: enable http3 for two ports
config.yaml
generated
nginx.conf
exmaple2: enable http3 for one port and disable http3 for another port.
config.yaml
generated
nginx.conf
Checklist