The configuration format for traffic_server is an extended form of that used by shadow.pl. Sections are dilinated by a line of the form [<config filename>]. Example:

[storage.config]

With exception of [records.config], [remap.config], and [meta] the contents between that tag and next file tag (or end of file) are written verbatim to a file of that name in that run_dir/config for that Traffic Server instance.

[records.config] section is processed specially using the shadow.pl format. Lines can can consist of two forms. The first gives a variable name and new value to substitute in. This form can only be used for variables that already present in records.config. Example:

proxy.config.hostdb.size              50000

The second form is used for adding lines to end of records.config and is intended for setting variables not all already in the file. Example:

add CONFIG proxy.config.core_limit INT -1

[remap.config] section allow for substitution of variables from records.config to allows for reverse proxy tests. The ports for TS are not known until the TS's instantiator runs so we need a special syntax to have the instantiator do substitution into the remap.config file. [remap.config] supports substitutions of the form &&(records_config_var). The named records.config var will be substituted in when the remap.config file is written. Example:

map http://%%(ts1):&&(proxy.config.http.server_port)/ \
http://%%(load1):%%(load1:server)/ 

The [meta] sections is where the instantiator is told about attributes that affect its work. The there is only currently one option which is tell the instantiator to start up traffic_manager instead of traffic_server. Here's how:

[meta]

run_manager: 1

• rafPort - RAF service port
• tsHttpPort - HTTP Proxy Port
• tsRtspPort - RTSP Proxy Port

• rafPort - RAF service port
• server - jtest http server port

Two lines of the form:

proxy_host: <hostname>
proxy_port: <http_port>