trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [trafficserver] branch master updated: Rename remaining references to ip_allow.config to ip_allow.yaml
Date Wed, 07 Aug 2019 22:38:52 GMT
This is an automated email from the ASF dual-hosted git repository.

bcall pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new 55c5194  Rename remaining references to ip_allow.config to ip_allow.yaml
55c5194 is described below

commit 55c51946bec84508fbb96f965246d3fd58e5cb83
Author: Randall Meyer <>
AuthorDate: Wed Aug 7 09:01:54 2019 -0700

    Rename remaining references to ip_allow.config to ip_allow.yaml
 configs/ip_allow.yaml.default                                         | 4 ++--
 doc/admin-guide/configuration/cache-basics.en.rst                     | 2 +-
 doc/admin-guide/files/index.en.rst                                    | 4 ++--
 .../files/{ip_allow.config.en.rst => ip_allow.yaml.en.rst}            | 0
 doc/admin-guide/monitoring/error-messages.en.rst                      | 4 ++--
 doc/admin-guide/plugins/remap_purge.en.rst                            | 2 +-
 doc/admin-guide/security/index.en.rst                                 | 4 ++--
 doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst         | 2 +-
 doc/                                                       | 2 +-
 src/traffic_layout/                                            | 2 +-
 10 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/configs/ip_allow.yaml.default b/configs/ip_allow.yaml.default
index f4d2233..ff3627d 100644
--- a/configs/ip_allow.yaml.default
+++ b/configs/ip_allow.yaml.default
@@ -1,9 +1,9 @@
-# ip_allow.config
+# ip_allow.yaml
 # Documentation:
 # Rules:
 # Each rule is a mapping, with the tags
diff --git a/doc/admin-guide/configuration/cache-basics.en.rst b/doc/admin-guide/configuration/cache-basics.en.rst
index 8416a04..f42c282 100644
--- a/doc/admin-guide/configuration/cache-basics.en.rst
+++ b/doc/admin-guide/configuration/cache-basics.en.rst
@@ -295,7 +295,7 @@ Configuring Traffic Server for PUSH Requests
 Before you can deliver content into your cache using HTTP ``PUSH``, you
 must configure Traffic Server to accept ``PUSH`` requests.
-#. Edit :file:`ip_allow.config` to allow ``PUSH`` from the appropriate addresses.
+#. Edit :file:`ip_allow.yaml` to allow ``PUSH`` from the appropriate addresses.
 #. Update :ts:cv:`proxy.config.http.push_method_enabled` in
diff --git a/doc/admin-guide/files/index.en.rst b/doc/admin-guide/files/index.en.rst
index 9d16bc3..caeb584 100644
--- a/doc/admin-guide/files/index.en.rst
+++ b/doc/admin-guide/files/index.en.rst
@@ -27,7 +27,7 @@ Configuration Files
-   ip_allow.config.en
+   ip_allow.yaml.en
@@ -47,7 +47,7 @@ Configuration Files
    Allows |TS| administrators to assign cache volumes to specific origin
    servers or domains.
    Controls access to the |TS| cache based on source IP addresses and networks
    including limiting individual HTTP methods.
diff --git a/doc/admin-guide/files/ip_allow.config.en.rst b/doc/admin-guide/files/ip_allow.yaml.en.rst
similarity index 100%
rename from doc/admin-guide/files/ip_allow.config.en.rst
rename to doc/admin-guide/files/ip_allow.yaml.en.rst
diff --git a/doc/admin-guide/monitoring/error-messages.en.rst b/doc/admin-guide/monitoring/error-messages.en.rst
index 407dd86..5e2400c 100644
--- a/doc/admin-guide/monitoring/error-messages.en.rst
+++ b/doc/admin-guide/monitoring/error-messages.en.rst
@@ -46,7 +46,7 @@ Process Warnings
 ``Connect by disallowed client <IP address>, closing``
    The specified client is not allowed to connect to Traffic Server;
-   the client IP address is not listed in the ``ip_allow.config`` file.
+   the client IP address is not listed in the ``ip_allow.yaml`` file.
 ``Could not rename log <filename> to <rolled filename>``
    System error when renaming log file during roll.
@@ -314,7 +314,7 @@ with corresponding HTTP response codes and customizable files.
 ``URI Too Long``
-   Could not process this request because the request uri 
+   Could not process this request because the request uri
    was too long ..
diff --git a/doc/admin-guide/plugins/remap_purge.en.rst b/doc/admin-guide/plugins/remap_purge.en.rst
index bae368a..14d783c 100644
--- a/doc/admin-guide/plugins/remap_purge.en.rst
+++ b/doc/admin-guide/plugins/remap_purge.en.rst
@@ -54,7 +54,7 @@ Configuration
 This plugin only functions as a remap plugin, and is therefore
 configured in :file:`remap.config`. Be aware that the ``PURGE`` requests
-are typically restricted to ``localhost``, but see :file:`ip_allow.config`
+are typically restricted to ``localhost``, but see :file:`ip_allow.yaml`
 and :file:`remap.config` how to configure these access controls.
 If PURGE does not work for your setup, you can enable a relaxed configuration
diff --git a/doc/admin-guide/security/index.en.rst b/doc/admin-guide/security/index.en.rst
index bbba4a8..9d51c32 100644
--- a/doc/admin-guide/security/index.en.rst
+++ b/doc/admin-guide/security/index.en.rst
@@ -33,7 +33,7 @@ Controlling Access
 Traffic Server can be configured to allow only certain clients to use
 the proxy cache.
-#. Add a line to :file:`ip_allow.config` for each IP address or
+#. Add a line to :file:`ip_allow.yaml` for each IP address or
    range of IP addresses allowed to access Traffic Server.
 #. Run the command :option:`traffic_ctl config reload` to apply the configuration
@@ -127,7 +127,7 @@ Client/Traffic Server connections, you must do the following:
    client certificates, or if you configure certificates to be optional and the
    connecting client does not present one, then access to Traffic Server is
    managed through other Traffic Server options that have been set (such as
-   rules in :file:`ip_allow.config`). ::
+   rules in :file:`ip_allow.yaml`). ::
         CONFIG proxy.config.ssl.client.certification_level INT 0
diff --git a/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst b/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst
index a657945..d2bcbc3 100644
--- a/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst
+++ b/doc/developer-guide/plugins/example-plugins/tls_bridge.en.rst
@@ -96,7 +96,7 @@ useful case.
    In this case |TS| will act as an open proxy which is unlikely to be a good idea. Therefore
    this approach is used |TS| will need to run in a restricted environment or use access
-   (via ``ip_allow.config`` or ``iptables``).
+   (via ``ip_allow.yaml`` or ``iptables``).
    If this is unsuitable then an identity remap rule can be added for the peer |TS|. If the
    |TS| was named "peer.ats" and it listens on port 4443, then the remap rule would be ::
diff --git a/doc/ b/doc/
index 97f90e3..5b6d3ca 100644
--- a/doc/
+++ b/doc/
@@ -39,7 +39,7 @@ man_pages = [
     ('admin-guide/files/cache.config.en', 'cache.config', u'Traffic Server cache configuration
file', None, '5'),
     ('admin-guide/files/hosting.config.en', 'hosting.config', u'Traffic Server domain hosting
configuration file', None, '5'),
-    ('admin-guide/files/ip_allow.config.en', 'ip_allow.config', u'Traffic Server IP access
control configuration file', None, '5'),
+    ('admin-guide/files/ip_allow.yaml.en', 'ip_allow.yam;', u'Traffic Server IP access control
configuration file', None, '5'),
     ('admin-guide/files/logging.yaml.en', 'logging.yaml', u'Traffic Server logging configuration
file', None, '5'),
     ('admin-guide/files/parent.config.en', 'parent.config', u'Traffic Server parent cache
configuration file', None, '5'),
     ('admin-guide/files/plugin.config.en', 'plugin.config', u'Traffic Server global plugin
configuration file', None, '5'),
diff --git a/src/traffic_layout/ b/src/traffic_layout/
index f826ea9..6b521ea 100644
--- a/src/traffic_layout/
+++ b/src/traffic_layout/
@@ -161,7 +161,7 @@ produce_layout(bool json)
   print_var("storage.config", RecConfigReadConfigPath("proxy.config.cache.storage_filename"),
   print_var("hosting.config", RecConfigReadConfigPath("proxy.config.cache.hosting_filename"),
   print_var("volume.config", RecConfigReadConfigPath("proxy.config.cache.volume_filename"),
-  print_var("ip_allow.config", RecConfigReadConfigPath("proxy.config.cache.ip_allow.filename"),
json, true);
+  print_var("ip_allow.yaml", RecConfigReadConfigPath("proxy.config.cache.ip_allow.filename"),
json, true);
   if (json) {

View raw message