162
Appendix D
Configuration Files
Format
The bypass rules have the following format:
Example
The following are example source, destination, and source/destination bypass rules:
bypass src 1.1.1.0/24, 25.25.25.25, 128.252.11.11 - 128.252.11.255
bypass dst 24.24.24.0/24
bypass src 25.25.25.25 AND dst 24.24.24.0
cache.config
The Traffic Server caches objects indexed by URLs. In the
cache.config
file, you can specify how a
particular group of URLs should be cached. The
cache.config
file contains caching rules that enable you
to specify:
•
Whether to cache objects
•
How long to pin particular objects in the cache
•
How long to consider cached objects as fresh
•
Whether to ignore no-cache directories from the server
Rule
Format
source IP bypass
bypass src IPaddress
Where
IPaddress
can be:
•
a simple IP address, such as 1.1.1.1
•
in CIDR (Classless Inter-Domain Routing) format, such as 1.1.1.0/24
•
a range separated by a dash, such as 1.1.1.1-2.2.2.2
•
any combination of the above, separated by commas, such as
1.1.1.0/24, 25.25.25.25, 123.1.23.1 - 123.1.23.123
destination IP bypass
bypass dst IPaddress
Where
IPaddress
has the same format as
src IPaddress
source/destination IP bypass
bypass src IPaddress
AND
dst IPaddress
Where
IPaddress
must be a single IP address, such as 1.1.1.1
IMPORTANT
After you modify the
bypass.config
file, Traffic Manager has to reread the
configuration files. Run the
traffic_line -x
command. If you are running a cluster,
you need only run the command for one node; the changes will propagate.
IMPORTANT
After you modify the
cache.config
file, Traffic Manager has to reread the
configuration files. Run the
traffic_line -x
command. If you are running a cluster,
you need only run the command for one node; the changes will propagate.
