Skip to content

Update the admin-guide hierachical caching and remap.config documentation. #6279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jrushford merged 1 commit into from
Dec 20, 2019
Merged

Update the admin-guide hierachical caching and remap.config documentation. #6279

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion doc/admin-guide/configuration/hierarchical-caching.en.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,11 @@ host name. This is true regardless of pristine host headers
(:ts:cv:`proxy.config.url_remap.pristine_host_hdr`) being enabled or not. The parent node
will receive the translated request (and thus needs to be configured to accept it).

:file:`remap.config` now also allows an alternative configuration that supports all the
**Parent Selection** policies and failover mentioned here using a new :file:`remap.config` tag,
**@strategy**. This eliminates the need for a second lookup against the remapped host name
required when using :file:`parent.config`. See using NextHop strategies with :file:`remap.config`,
:doc:`../../admin-guide/files/strategies.yaml.en`

Example
~~~~~~~
Expand Down Expand Up @@ -165,7 +170,11 @@ the configuration adjustments detailed below.
cache.

#. Edit :file:`parent.config` to set parent proxy rules which will specify the
parent cache to which you want missed requests to be forwarded.
parent cache to which you want missed requests to be forwarded. Or as an
alternative to :file:`parent.config`, edit :file:`strategies.yaml` to
specify next hop parent proxy rules and hosts. Then in :file:`remap.config`
use the **@strategy** tag to select the next hop parent proxy rules. See
:doc:`../../admin-guide/files/strategies.yaml.en`

The following example configures Traffic Server to route all requests
containing the regular expression ``politics`` and the path
Expand Down
7 changes: 7 additions & 0 deletions doc/admin-guide/files/remap.config.en.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -480,6 +480,13 @@ mapping rules. (It is activated before any mappings and is never
deactivated.) The filter `local_only` will only be applied to the
second mapping.

NextHop Selection Strategies
============================

You may configure Nexthop or Parent hierarchical caching rules by remap using the
**@strategy** tag. See :doc:`../configuration/hierarchical-caching.en` and :doc:`strategies.yaml.en`
for configuration details and examples.

Including Additional Remap Files
================================

Expand Down