trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zw...@apache.org
Subject [trafficserver] 07/07: Add note to background fetch about include/exclude (#7343)
Date Thu, 03 Dec 2020 19:36:30 GMT
This is an automated email from the ASF dual-hosted git repository.

zwoop pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git

commit a29ba2ac3f499886d8b64800e87165243c1ea4e9
Author: mlibbey <mlibbey@apache.org>
AuthorDate: Thu Nov 26 12:17:50 2020 -0800

    Add note to background fetch about include/exclude (#7343)
    
    The include configuraton directive for background fetch is a bit
    confusing, in that it requires a corresponding exclude directive.
    That is, its used as an exemption mechanism to an exclude
    directive.
    
    (cherry picked from commit 2c9d4c753aa5b946acc7876618f611dfd53203f1)
---
 doc/admin-guide/plugins/background_fetch.en.rst | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/admin-guide/plugins/background_fetch.en.rst b/doc/admin-guide/plugins/background_fetch.en.rst
index 1e2f511..8f28a7e 100644
--- a/doc/admin-guide/plugins/background_fetch.en.rst
+++ b/doc/admin-guide/plugins/background_fetch.en.rst
@@ -74,6 +74,16 @@ The contents of the config-file could be as below::
    exclude X-Foo-Bar text
    exclude Content-Length <1000
 
+.. important::
+
+   The ``include`` configuration directive is only used when there is a corresponding ``exclude``
to exempt.
+   For example, a single line directive, ``include Host example.com`` would not make the
plugin
+   *only* act on example.com. To acheive classic allow (only) lists, one would need to have
a broad
+   exclude line, such as::
+
+      exclude Host *
+      include Host example.com
+
 The plugin also now supports per remap activation. To activate the plugin for a given remap,
add the
 below on the remap line::
 


Mime
View raw message