You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ml...@apache.org on 2016/05/10 19:46:58 UTC
[trafficserver] branch master updated (4d61d7b -> caa402c)
This is an automated email from the ASF dual-hosted git repository.
mlibbey pushed a change to branch master
in repository https://git-dual.apache.org/repos/asf/trafficserver.git.
from 4d61d7b TS-4420: Fix TSHttpTxnParentProxySet crash on parent failure.
new 6903698 Fix Geo section markup
new caa402c Cleanup regex_remap vs regex_map references
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
doc/admin-guide/files/remap.config.en.rst | 6 +++---
doc/admin-guide/plugins/header_rewrite.en.rst | 3 ++-
2 files changed, 5 insertions(+), 4 deletions(-)
--
To stop receiving notification emails like this one, please contact
['"commits@trafficserver.apache.org" <co...@trafficserver.apache.org>'].
[trafficserver] 02/02: Cleanup regex_remap vs regex_map references
Posted by 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>.
[trafficserver] 01/02: Fix Geo section markup
Posted by 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 6903698326e088a32b719076453f8aad070e2320
Author: Miles Libbey <ml...@apache.org>
AuthorDate: Mon May 9 13:19:59 2016 -0700
Fix Geo section markup
---
doc/admin-guide/plugins/header_rewrite.en.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/admin-guide/plugins/header_rewrite.en.rst b/doc/admin-guide/plugins/header_rewrite.en.rst
index 1576450..213ec74 100644
--- a/doc/admin-guide/plugins/header_rewrite.en.rst
+++ b/doc/admin-guide/plugins/header_rewrite.en.rst
@@ -218,11 +218,12 @@ as documented in `URL Parts`_ below.
GEO
~~~
::
+
cond %{GEO:<part>} <operand>
Perform a GeoIP lookup of the client-IP, using a 3rd party library and
DB. Currently only the MaxMind GeoIP API is supported. The default is to
-do a Country lookup, but the following qualifiers are supported:
+do a Country lookup, but the following qualifiers are supported::
%{GEO:COUNTRY} The country code (e.g. "US")
%{GEO:COUNTRY-ISO} The country ISO code (e.g. 225)
--
To stop receiving notification emails like this one, please contact
"commits@trafficserver.apache.org" <co...@trafficserver.apache.org>.