Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Configuration Files > parent.config
The parent.config file identifies the HTTP parent proxies used in an HTTP cache hierarchy. Use this file to perform the following configuration:
Content Gateway uses the parent.config file only when the HTTP parent caching option is enabled. See Configuring Content Gateway to use an HTTP parent cache.
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.
Each line in the parent.config file must contain a parent caching rule. Content Gateway recognizes three space-delimited tags:
primary_destination=value secondary_specifier=value action=value
Secondary specifiers are optional in the parent.config file. The following table lists the possible secondary specifiers and their allowed values.
*
*
*
*
true - Content Gateway goes through the parent cache list in a round-robin based on client IP address.
*
strict - Content Gateway machines serve requests strictly in turn. For example, machine proxy1 serves the first request, proxy2 serves the second request, and so on.
*
false - round-robin selection does not occur.
*
true - requests bypass parent hierarchies and go directly to the origin server.
*
false - requests do not bypass parent hierarchies.
The following rule configures a parent cache hierarchy consisting of Content Gateway (which is the child) and two parents, p1.x.com and p2.x.com. The proxy forwards the requests it cannot serve to the parent servers p1.x.com and p2.x.com in a round-robin fashion because round_robin=true.
The following rule configures Content Gateway to route all requests containing the regular expression politics and the path /viewpoint directly to the origin server (bypassing any parent hierarchies):
Important 
Every line in the parent.config file must contain either a parent= or go_direct= directive.
A bypass rule that includes parent= and go_direct=true, causes the specified dest_domain to be sent to the parent while all other domains are bypassed (the opposite of the usual intended action).

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Configuration Files > parent.config