documentation for parameters
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/ba8bc3dd Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/ba8bc3dd Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/ba8bc3dd Branch: refs/heads/master Commit: ba8bc3dde442626c7524a6e6188ca4fc5cd50b24 Parents: 2b05eaf Author: Derek Gelinas <mrdgeli...@gmail.com> Authored: Wed Mar 15 19:46:29 2017 +0000 Committer: Jeremy Mitchell <mitchell...@gmail.com> Committed: Thu Mar 16 15:08:24 2017 -0600 ---------------------------------------------------------------------- docs/source/admin/traffic_ops_config.rst | 6 ++++++ 1 file changed, 6 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/ba8bc3dd/docs/source/admin/traffic_ops_config.rst ---------------------------------------------------------------------- diff --git a/docs/source/admin/traffic_ops_config.rst b/docs/source/admin/traffic_ops_config.rst index 89ff265..4c8038f 100644 --- a/docs/source/admin/traffic_ops_config.rst +++ b/docs/source/admin/traffic_ops_config.rst @@ -40,6 +40,7 @@ Many of the settings for the different servers in a Traffic Control CDN are cont +==========================+===============+=======================================================================================================================================+ | tm.url | global | The URL where this Traffic Ops instance is being served from. | +--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ +| tm.cache.url | global | Not Requred. The URL where the Traffic Ops Config file cache instance is being served from. Requires Traffic Ops 2.1 and above. |+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ | tm.toolname | global | The name of the Traffic Ops tool. Usually "Traffic Ops". Used in the About screen and in the comments headers of the files generated. | +--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+ | tm.infourl | global | This is the "for more information go here" URL, which is visible in the About page. | @@ -151,6 +152,11 @@ Content Purge is controlled by the following parameters in the profile of the ca | regex_revalidate | plugin.config | The config to be used for regex_revalidate. | `regex_revalidate <https://docs.trafficserver.apache.org/en/5.3.x/reference/plugins/regex_remap.en.html>`_ | | | | For example: --config regex_revalidate.config | | +----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+ +| use_reval_pending | global | Configures Traffic Ops to use separate reval_pending flag for each cache. When this flag is in use ORT will check for a new regex_revalidate.config every 60 seconds in syncds mode during | +| | | the dispersal timer. This will also allow ORT to be run in revalidate mode, which will check for and clear the reval_pending flag. This can be set to run via cron task. | +| | | This value is set to 0 by default. Enable with a value of 1. Use of this feature requires Traffic Ops 2.1 and above. | ++----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+ + Note that the TTL the adminstrator enters in the purge request should be longer than the TTL of the content to ensure the bad content will not be used. If the CDN is serving content of unknown, or unlimited TTL, the administrator should consider using `proxy-config-http-cache-guaranteed-min-lifetime <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-config-http-cache-guaranteed-min-lifetime>`_ to limit the maximum time an object can be in the cache before it is considered stale, and set that to the same value as `maxRevalDurationDays` (Note that the former is in seconds and the latter is in days, so convert appropriately).
