Enables or disables the HTTP parent caching option. When this option is enabled, Content Gateway can participate in an HTTP cache hierarchy. You can point your Content Gateway server at a parent network cache (either another Content Gateway server or a different caching product) to form a cache hierarchy where a child cache relies upon a parent cache in fulfilling client requests.) See HTTP cache hierarchies.

If rules in the parent.config file are set so that only selected requests are sent to a parent proxy, Content Gateway skips name resolution only for requests that are going to the parent proxy. Name resolution is performed as usual for requests that are not sent to a parent proxy. If the parent proxy is down and the child proxy can go directly to origin servers, the child performs DNS resolution.

Displays a table listing the rules in the parent.config file that identify the HTTP parent proxies used in an HTTP cache hierarchy and configure selected URL requests to bypass parent proxies.

Updates the table to display the most up-to-date rules in the parent.config file.

Opens the configuration file editor so that you can edit and add rules to the parent.config file.

Lists the parent.config file rules. Select a rule to edit it. The buttons on the left of the box allow you to delete or move the selected rule up or down in the list.

dest_domain is a requested domain name.

dest_host is a requested hostname.

dest_ip is a requested IP address.

url_regex is a regular expression to be found in a URL.

If the primary destination is dest_domain, a value for this field can be yahoo.com

If the primary destination type is dest_ip, the value for this field can be 123.456.78.9.

If the primary destination is url_regex, a value for this field can be politics.

Specifies the IP addresses or hostnames of the parent proxies and the port numbers used for communication. Parent proxies are queried in the order specified in the list. If the request cannot be handled by the last parent server in the list, it is routed to the origin server. Separate each entry with a semicolon; for example: parent1:8080; parent2:8080

Select true for the proxy to go through the parent cache list in a round-robin based on client IP address.

Select strict for the proxy to serve requests strictly in turn. For example, machine proxy1 serves the first request, proxy2 serves the second request, and so on.

Select false if you do not want round-robin selection to occur.

Select true for requests to bypass parent hierarchies and go directly to the origin server.

Select false if you do not want requests to bypass parent hierarchies.