[trafficserver] 02/02: Cleanup regex_remap vs regex_map references

[ml...@apache.org]

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

mlibbey pushed a commit to branch master
in repository https://git-dual.apache.org/repos/asf/trafficserver.git

commit caa402c5fef7ae1ceef732b22c2d7c71c6e51e92
Author: Miles Libbey <ml...@apache.org>
AuthorDate: Mon May 9 13:21:23 2016 -0700

    Cleanup regex_remap vs regex_map references
---
 doc/admin-guide/files/remap.config.en.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/admin-guide/files/remap.config.en.rst b/doc/admin-guide/files/remap.config.en.rst
index 209d7ac..3c994ae 100644
--- a/doc/admin-guide/files/remap.config.en.rst
+++ b/doc/admin-guide/files/remap.config.en.rst
@@ -267,13 +267,13 @@ limitations below:
 
 -  Only the ``host`` field can contain a regex; the ``scheme``,
    ``port``, and other fields cannot. For path manipulation via regexes,
-   use the ``regex_remap`` plugin.
+   use the :ref:`admin-plugins-regex-remap`.
 -  The number of capturing subpatterns is limited to 9. This means that
    ``$0`` through ``$9`` can be used as subtraction placeholders (``$0``
    will be the entire input string).
 -  The number of substitutions in the expansion string is limited to 10.
 -  There is no ``regex_`` equivalent to ``reverse_remap``, so when using
-   ``regex_remap`` you should make sure the reverse path is clear by
+   ``regex_map`` you should make sure the reverse path is clear by
    setting (:ts:cv:`proxy.config.url_remap.pristine_host_hdr`)
 
 Examples
@@ -394,7 +394,7 @@ Examples
 
     map http://foo.example.com/  http://foo.example.com/ @action=deny @src_ip=1.2.3.4
     map http://foo.example.com/  http://foo.example.com/ @action=allow @src_ip=127.0.0.1
-    
+
     map http://foo.example.com/  http://foo.example.com/ @action=allow @src_ip=10.5.2.1 @in_ip=72.209.23.4
 
     map http://foo.example.com/  http://foo.example.com/ @action=allow @src_ip=127.0.0.1 @method=post @method=get @method=head

-- 
To stop receiving notification emails like this one, please contact
"commits@trafficserver.apache.org" <co...@trafficserver.apache.org>.