trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a..@apache.org
Subject [trafficserver] branch master updated: Doc: Fix "dst_ip" typo in ip_allow.config documentation.
Date Wed, 05 Dec 2018 15:49:26 GMT
This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/master by this push:
     new 9c9d446  Doc: Fix "dst_ip" typo in ip_allow.config documentation.
9c9d446 is described below

commit 9c9d446c869276f75ce4061f65bd2939f0f25a38
Author: Alan M. Carroll <amc@apache.org>
AuthorDate: Tue Dec 4 13:23:23 2018 -0600

    Doc: Fix "dst_ip" typo in ip_allow.config documentation.
---
 doc/admin-guide/files/ip_allow.config.en.rst | 4 ++--
 proxy/http/remap/AclFiltering.h              | 2 +-
 proxy/http/remap/RemapConfig.cc              | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/admin-guide/files/ip_allow.config.en.rst b/doc/admin-guide/files/ip_allow.config.en.rst
index 537afcb..b313f83 100644
--- a/doc/admin-guide/files/ip_allow.config.en.rst
+++ b/doc/admin-guide/files/ip_allow.config.en.rst
@@ -39,7 +39,7 @@ format::
     dest_ip=<range of IP addresses> action=<action> [method=<list of methods
separated by '|'>]
 
 For ``src_ip`` the remote inbound connection address, i.e. the IP address of the client,
is checked
-against the specified range of IP addresses. For ``dst_ip`` the outbound remote address (i.e.
the IP
+against the specified range of IP addresses. For ``dest_ip`` the outbound remote address
(i.e. the IP
 address to which |TS| connects) is checked against the specified IP address range.
 
 Range specifications can be IPv4 or IPv6, but any single range must be one or the other.
Ranges can
@@ -67,7 +67,7 @@ For each inbound or outbound connection the applicable rule is selectd by
first
 address. The rule is then applied (if the method matches) or its opposite is applied (if
the method
 doesn't match). If no rule is matched access is allowed. This makes each rule both an accept
and
 deny, one explicit and the other implicit. The ``src_ip`` rules are checked when a host connects
-to |TS|. The ``dst_ip`` rules are checked when |TS| connects to another host.
+to |TS|. The ``dest_ip`` rules are checked when |TS| connects to another host.
 
 By default the :file:`ip_allow.config` file contains the following lines, which allows all
methods
 to connections from localhost and denies the ``PUSH``, ``PURGE`` and ``DELETE`` methods to
all other
diff --git a/proxy/http/remap/AclFiltering.h b/proxy/http/remap/AclFiltering.h
index f9cb8c8..a4af726 100644
--- a/proxy/http/remap/AclFiltering.h
+++ b/proxy/http/remap/AclFiltering.h
@@ -91,7 +91,7 @@ public:
   src_ip_info_t src_ip_array[ACL_FILTER_MAX_SRC_IP];
 
   // in_ip
-  int in_ip_cnt; // how many valid dst_ip rules we have
+  int in_ip_cnt; // how many valid dest_ip rules we have
   src_ip_info_t in_ip_array[ACL_FILTER_MAX_IN_IP];
 
   acl_filter_rule();
diff --git a/proxy/http/remap/RemapConfig.cc b/proxy/http/remap/RemapConfig.cc
index 0feefdf..c0eab6e 100644
--- a/proxy/http/remap/RemapConfig.cc
+++ b/proxy/http/remap/RemapConfig.cc
@@ -529,7 +529,7 @@ remap_validate_filter_args(acl_filter_rule **rule_pp, const char **argv,
int arg
       }
     }
 
-    if (ul & REMAP_OPTFLG_IN_IP) { /* "dst_ip=" option */
+    if (ul & REMAP_OPTFLG_IN_IP) { /* "dest_ip=" option */
       if (rule->in_ip_cnt >= ACL_FILTER_MAX_IN_IP) {
         Debug("url_rewrite", "[validate_filter_args] Too many \"in_ip=\" filters");
         snprintf(errStrBuf, errStrBufSize, "Defined more than %d \"in_ip=\" filters!", ACL_FILTER_MAX_IN_IP);


Mime
View raw message