Clarify in the docs matching by wildcard of the sni_domains field in listener components #3371
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.
title: sni_domains: clarify in the documentation matching by a wildcard
Description:
According to
envoy/source/common/ssl/context_manager_impl.cc
Line 116 in a22159a
the wildcard is allowed before the first dot, it means that
www.example.com
will be matched by an SNI domain*.example.com
, but not by*.com
or*
. The proposed PR changes the docs to explain it.Risk Level: Low
Testing:
Documentation change, no testing.
Docs Changes:
The PR is a docs change only.
Release Notes:
None.
Fixes #3363 .