Configuration Files

cache.config

Defines if, how, and for what durations Traffic Server caches objects, based on destinations, clients, URL components, and more.

hosting.config

Allows Traffic Server administrators to assign cache volumes to specific origin servers or domains.

ip_allow.yaml

Controls access to the Traffic Server cache based on source IP addresses and networks including limiting individual HTTP methods.

logging.yaml

Defines custom log file formats, filters, and processing options.

parent.config

Configures parent proxies in hierarchical caching layouts.

plugin.config

Control runtime loadable plugins available to Traffic Server, as well as their configurations.

records.config

Contains many configuration variables affecting Traffic Server operation.

remap.config

Defines mapping rules used by Traffic Server to properly route all incoming requests.

splitdns.config

Configures DNS servers to use under specific conditions.

ssl_multicert.config

Configures Traffic Server to use different server certificates for SSL termination when listening on multiple addresses or when clients employ SNI.

sni.yaml

Configures SNI based Layer 4 routing.

storage.config

Configures all storage devices and paths to be used for the Traffic Server cache.

strategies.yaml

Configures NextHop strategies used with remap.config

volume.config

Defines cache space usage by individual protocols.

Note

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 #.