Defines if, how, and for what durations Traffic Server caches objects, based on destinations, clients, URL components, and more.
Allows Traffic Server administrators to assign cache volumes to specific origin servers or domains.
Controls access to the Traffic Server cache based on source IP addresses and networks including limiting individual HTTP methods.
Defines custom log file formats, filters, and processing options.
Configures parent proxies in hierarchical caching layouts.
Control runtime loadable plugins available to Traffic Server, as well as their configurations.
Contains many configuration variables affecting Traffic Server operation.
Defines mapping rules used by Traffic Server to properly route all incoming requests.
Configures DNS servers to use under specific conditions.
Configures Traffic Server to use different server certificates for SSL termination when listening on multiple addresses or when clients employ SNI.
Configures SNI based Layer 4 routing.
Configures all storage devices and paths to be used for the Traffic Server cache.
Configures NextHop strategies used with remap.config
Defines cache space usage by individual protocols.
Currently the YAML parsing library has a bug where line number counting (for error messages) ignores comment lines that start with #. A work-around is to put a space before the #.