You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by zw...@apache.org on 2018/08/07 20:11:11 UTC

[trafficserver] branch 8.0.x updated: Fix tunnel routing documentation

This is an automated email from the ASF dual-hosted git repository.

zwoop pushed a commit to branch 8.0.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git


The following commit(s) were added to refs/heads/8.0.x by this push:
     new f93901f  Fix tunnel routing documentation
f93901f is described below

commit f93901f962779ca0d258544431eabba65a3af01d
Author: Pushkar Pradhan <pp...@oath.com>
AuthorDate: Thu Aug 2 22:46:23 2018 -0700

    Fix tunnel routing documentation
    
    (cherry picked from commit 0fa8970bcaebf095f8134da65ccf646f309e1d0f)
---
 doc/admin-guide/layer-4-routing.en.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/admin-guide/layer-4-routing.en.rst b/doc/admin-guide/layer-4-routing.en.rst
index 86c22b0..8739d38 100644
--- a/doc/admin-guide/layer-4-routing.en.rst
+++ b/doc/admin-guide/layer-4-routing.en.rst
@@ -113,6 +113,13 @@ The :file:`ssl_server_name.yaml` contents would be
       }
    }
 
+In addition to this, in the :file:`records.config` file, edit the following variables:
+
+   -  :ts:cv:`proxy.config.http.connect_ports`: ``443 4443`` to allow |TS| to connect
+      to the destination port
+   -  :ts:cv:`proxy.config.url_remap.remap_required`: 0 to permit |TS| to process requests
+      for hosts not explicitly configured in the remap rules
+
 The sequence of network activity for a Client connecting to ``service-2`` is
 
 .. image:: ../uml/images/l4-sni-routing-seq.svg