plugin.config¶

Description¶

The plugin.config file controls run-time loadable plugins available to Traffic Server, as well as their configuration. Plugins listed in this file are referred to as global plugins because they are always loaded and have global effect. This is in contrast to plugins specified in remap.config, whose effects are limited to the specific mapping rules to which they are applied.

Each configuration line consists of a path to an .so file. This path can either be absolute, or relative to the plugin directory (usually /usr/local/libexec/trafficserver). Failure to load a plugin is fatal, and will cause Traffic Server to abort. In general, it is not possible to know whether it is safe for the service to run without a particular plugin, since plugins can have arbitrary effects on caching and authorization policies.

Important

Plugins should only be listed once. The order in which the plugins are listed is also the order in which they are chained for request processing.



See Also¶

TSAPI(3ts), TSPluginInit(3ts), remap.config(5)