fix: support QUIC listeners with multiple filter chains for different hostnames #7843
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 PR adds HTTP/3
filter chain matchersupport for QUIC listeners to honor multiple hostnames/certificates (SNI) like TCP/TLS listeners.TCL/TLS listeners are unchanged. They still use filterChainMatch and TLS inspector listener filter to match on SNI, so this won't break existing EnvoyPatchPolicies and Extension servers.Update: this PR still uses filter_chain_match.server_names for QUIC listener. Envoy’s QUIC stack parses SNI itself, so filter_chain_match.server_names works without TLS Inspector for QUIC listeners. TLS Inspector is only needed for TCP/TLS listeners.
Fixes: #5660