@@ -40,36 +40,34 @@ regular expression against your origin URLs permits. Thus, individual cache
4040objects may have rules created for them, or entire path prefixes, or even any
4141cache objects with a particular file extension.
4242
43- Installation
44- ============
45-
46- To make this plugin available, you must enable experimental plugins when
47- building |TS |::
48-
49- ./configure --enable-experimental-plugins
50-
5143Configuration
5244=============
45+ .. program :: regex_revalidate.so
5346
54- This plugin is enabled via the :file: `plugin.config ` configuration file, with
55- two required arguments: the path to a rules file, and the path to a log file::
47+ `` Regex Revalidate `` is a global plugin and is configured via :file: `plugin.config `.
48+ .. option :: --config < path to revalidate rules > (also -c)
5649
57- regex_revalidate.so -c <path to rules> -l <path to log>
50+ (`required `) - specifies the file which contains the revalidation rules.
51+ The rule configuration file format is described below in
52+ `Revalidation Rules `_. These rules are always reloaded when
53+ ``traffic_ctl config reload `` is invoked.
5854
59- The rule configuration file format is described below in ` Revalidation Rules `_.
55+ .. option :: --log < path to log > (also -l)
6056
61- By default The plugin regularly (every 60 seconds) checks its rules configuration
62- file for changes and it will also check for changes when ``traffic_ctl config reload ``
63- is run. If the file has been modified since its last scan, the contents
64- are read and the in-memory rules list is updated. Thus, new rules may be added and
65- existing ones modified without requiring a service restart.
57+ (`optional `) - specifies path to rule logging. This log is written to
58+ after rule changes and contains the current active ruleset. If missing
59+ no log file is generated.
6660
67- The configuration parameter `--disable-timed-updates ` or `-d ` may be used to configure
68- the plugin to disable timed config file change checks. With timed checks disabled,
69- config file changes are checked are only when ``traffic_ctl config reload `` is run.::
61+ .. option :: --disable-timed-reload (also -d)
7062
71- regex_revalidate.so -d -c <path to rules> -l <path to log>
63+ (`optional `) - default plugin behaviour is to check the revalidate
64+ rules file for changes every 60 seconds. This option disables the
65+ checking.
7266
67+ ``traffic_ctl `` <command>
68+ * ``traffic_ctl config reload `` - triggers a reload of the rules file. If there are no changes then the loaded rules are discarded.
69+ * ``traffic_ctl plugin msg regex_revalidate config_reload `` - triggers a reload of the rules file apart from a full config reload.
70+ * ``traffic_ctl plugin msg regex_revalidate config_print `` - writes the current active ruleset to :file: `traffic.out `
7371
7472Revalidation Rules
7573==================
@@ -111,11 +109,11 @@ the fact that the plugin uses :c:data:`TS_HTTP_CACHE_LOOKUP_COMPLETE_HOOK`.
111109Removing Rules
112110--------------
113111
114- While new rules are added dynamically (the configuration file is checked every
115- 60 seconds for changes), rule lines removed from the configuration file do not
116- currently lead to that rule being removed from the running plugin. In these
117- cases, if the rule must be taken out of service, a service restart may be
118- necessary .
112+ While new rules are added dynamically (the configuration file is checked
113+ every 60 seconds for changes), rule lines removed from the configuration
114+ file do not currently lead to that rule being removed from the running
115+ plugin. To take these rules out of service the rule should be assigned a
116+ new time in the past which will cause it to be pruned during reload phase .
119117
120118Examples
121119========
0 commit comments