Important  After you modify this file, run content_line -x from the Content Gateway bin directory (/opt/WCG/bin) to apply the changes. When you apply the changes to a node in a cluster, Content Gateway applies the changes to all nodes in the cluster.

Primary Destination	Allowed Value
dest_domain	A requested domain name
dest_host	A requested hostname
dest_ip	A requested IP address
url_regex	A regular expression to be found in a URL

Note  You can use more than one secondary specifier in a rule. However, you cannot repeat a secondary specifier.

Secondary Specifier	Allowed Value
port	A requested URL port
scheme	A request URL protocol; one of the following: HTTP FTP
prefix	A prefix in the path part of a URL
suffix	A file suffix in the URL
method	A request URL method; one of the following: get put trace
time	A time range, such as 08:00-14:00
src_ip	A client IP address.
user_agent	A request header User-Agent value.

Action	Value
action	One of the following values: never-cache configures the proxy to never cache specified objects. ignore-no-cache configures the proxy to ignore all Cache-Control: no-cache headers. ignore-client-no-cache configures the proxy to ignore Cache-Control: no-cache headers from client requests. ignore-server-no-cache configures the proxy to ignore Cache-Control: no-cache headers from origin server responses.
pin-in-cache	The amount of time you want to keep the object(s) in the cache. The following time formats are allowed: d for days (for example 2d) h for hours (for example, 10h) m for minutes (for example, 5m) s for seconds (for example, 20s) mixed units (for example, 1h15m20s)
revalidate	The amount of time you want to consider the object(s) fresh. Use the same time formats as pin-in-cache.
ttl-in-cache	The amount of time you want to keep objects in the cache regardless of Cache-Control response headers. Use the same time formats as pin-in-cache and revalidate.

Note  The rules are applied in the order listed.