[trafficserver] branch header_doc updated (cf92713 -> 2341fcd)

[bc...@apache.org]

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

bcall pushed a change to branch header_doc
in repository https://gitbox.apache.org/repos/asf/trafficserver.git.


 discard cf92713  Update the header_rewrite doc for clarification on CLIENT-URL:HOST.
     new 2341fcd  Update the header_rewrite doc for clarification on CLIENT-URL:HOST

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (cf92713)
            \
             N -- N -- N   refs/heads/header_doc (2341fcd)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 lib/ts/Makefile.am                         |   6 +-
 lib/ts/unit-tests/test_IntrusiveHashMap.cc | 307 +----------------------------
 plugins/header_rewrite/conditions.cc       |   4 -
 proxy/hdrs/URL.h                           |   1 -
 4 files changed, 7 insertions(+), 311 deletions(-)

[trafficserver] 01/01: Update the header_rewrite doc for clarification on CLIENT-URL:HOST

[bc...@apache.org]

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

bcall pushed a commit to branch header_doc
in repository https://gitbox.apache.org/repos/asf/trafficserver.git

commit 2341fcdf6501bbd4ea0d0f86d1e25feeb6e6922b
Author: Bryan Call <bc...@apache.org>
AuthorDate: Mon Aug 27 10:32:57 2018 -0700

    Update the header_rewrite doc for clarification on CLIENT-URL:HOST
---
 doc/admin-guide/plugins/header_rewrite.en.rst | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/admin-guide/plugins/header_rewrite.en.rst b/doc/admin-guide/plugins/header_rewrite.en.rst
index 50fbf1d..48060e6 100644
--- a/doc/admin-guide/plugins/header_rewrite.en.rst
+++ b/doc/admin-guide/plugins/header_rewrite.en.rst
@@ -197,6 +197,11 @@ rule is evaluated, this condition will always operate on the original, unmapped
 URL supplied by the client. The ``<part>`` may be specified according to the
 options documented in `URL Parts`_.
 
+Note that the HOST ``<part>`` of the CLIENT-URL might not be set until the remap
+phase of the transaction.  This happens when there is no host in the incoming URL
+and only set as a host header.  During the remap phase the host header is copied
+to the CLIENT-URL.  Use CLIENT-HEADER:Host if you are going to match the host.
+
 COOKIE
 ~~~~~~
 ::