181
Appendix D
Configuration Files
The following tables lists the possible actions and their allowed values:
Example
The following rule sets up a parent cache hierarchy consisting of the Traffic Server (which is the child) and
two parents,
p1
and
p2
. All
get
requests, if they cannot be served by the Traffic Server, are routed to the first
parent server,
p1.x.com
. If they are not in the first parent server, they are routed to the second parent server,
p2.y.com
. Because
round_robin=true
, the parent servers are queried in a round robin fashion.
dest_domain=. method=get parent=”p1.x.com:8080; p2.y.com:8080” round_robin=true
The following rule tells the Traffic Server to route all requests containing the regular expression
politics
and the path
/viewpoint
directly to the origin server (bypassing any parent hierarchies).
url_regex=politics prefix=/viewpoint go_direct=true
Every line in the
parent.config
file must contain either a
parent=
or
go_direct=
directive.
A parent cache entry in the Parent Caching section of the Routing page, described on page 53, is entered as
the bottom line in the
parent.config
file (meaning that this entry serves as a default). For example, if you
enter
parent1:8080
in the
Parent Cache
field on the Routing page, the following line is entered at the
bottom of the
parent.config
file:
dest_domain=. parent=parent1:8080
partition.config
The
partition.config
file lets you manage your cache space more efficiently and restrict disk usage by
creating cache partitions of different sizes for specific protocols. You can further configure these partitions to
store data from certain origin servers and/or domains in the
hosting.config
file (refer to
hosting.config‚ on
page 166
).
For step by step instructions on partitioning the cache, refer to
Partitioning the cache‚ on page 59
.
You must stop Traffic Server before you change the cache partition size and protocol assignment.
Action
Allowed Value
parent
Enter an ordered list of parent proxies. If the request cannot be handled by the
last parent server in the list, it will be routed to the origin server.
round_robin
•
true
Enter true if you want the Traffic Server to go through the parent cache list in a
round robin.
•
strict
Enter strict if you want Traffic Server machines to serve requests strictly in
turn. For example, machine ts-sun8 serves the first request, ts-sun9 serves the
second request, and so on.
•
false
Enter false if you do not want round robin selection to occur.
go_direct
•
true
Enter true if you want requests to bypass parent hierarchies and go directly to
the origin server.
•
false
Enter false if you do not want requests to bypass parent hierarchies.
IMPORTANT
The partition configuration must be the same on all nodes in a cluster.