This is an automated email from the ASF dual-hosted git repository. zwoop pushed a commit to branch CleanupWS9.x in repository https://gitbox.apache.org/repos/asf/trafficserver.git
commit 7c4d9be38970d6e1a6d8f9ab652587e4d0331726 Author: Randall Meyer <r...@apache.org> AuthorDate: Fri Nov 1 16:09:39 2019 -0700 Fixes misc. spelling and whitespace (cherry picked from commit 6ef4db40f24f707bbd05d5ef05cb2e4b5d35f91b) Conflicts: doc/release-notes/upgrading.en.rst doc/release-notes/whats-new.en.rst --- doc/admin-guide/files/records.config.en.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/admin-guide/files/records.config.en.rst b/doc/admin-guide/files/records.config.en.rst index 56a5645..e710de9 100644 --- a/doc/admin-guide/files/records.config.en.rst +++ b/doc/admin-guide/files/records.config.en.rst @@ -3473,21 +3473,21 @@ Client-Related Configuration Indicate how the SNI value for the TLS connection to the origin is selected. By default it is `host` which means the host header field value is used for the SNI. If `remap` is specified, the - remapped origin name is used for the SNI value. If `verify_with_name_source` is specified, the - SNI will be the host header value and the name to check in the server certificate will be the + remapped origin name is used for the SNI value. If `verify_with_name_source` is specified, the + SNI will be the host header value and the name to check in the server certificate will be the remap header value. - We have two names that could be used in the transaction host header and the SNI value to the - origin. These could be the host header from the client or the remap host name. Unless you have + We have two names that could be used in the transaction host header and the SNI value to the + origin. These could be the host header from the client or the remap host name. Unless you have pristine host header enabled, these are likely the same values. If sni_policy = host, both the sni and the host header to origin will be the same. - If sni_policy = remap, the sni value with be the remap host name and the host header will be the + If sni_policy = remap, the sni value with be the remap host name and the host header will be the host header from the client. - In addition, We may want to set the SNI and host headers the same (makes some common web servers - happy), but the certificate served by the origin may have a name that corresponds to the remap - name. So instead of using the SNI name for the name check, we may want to use the remap name. - So if sni_policy = verify_with_name_source, the sni will be the host header value and the name to + In addition, We may want to set the SNI and host headers the same (makes some common web servers + happy), but the certificate served by the origin may have a name that corresponds to the remap + name. So instead of using the SNI name for the name check, we may want to use the remap name. + So if sni_policy = verify_with_name_source, the sni will be the host header value and the name to check in the server certificate will be the remap header value. - + .. ts:cv:: CONFIG proxy.config.ssl.client.TLSv1 INT 0