Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Hierarchical Caching > HTTP cache hierarchies
HTTP cache hierarchies
Help | Content Gateway | v8.4.x
In an HTTP cache hierarchy, if a Content Gateway node cannot find a requested object in its cache, it can search a parent cache—which itself can search other caches—before resorting to retrieving the object from the origin server. See Configuring Content Gateway to use an HTTP parent cache.
*
You can configure a Content Gateway node to use one or more HTTP parent caches, so that if one parent is unavailable, another parent can service requests. This is called parent failover and is described below.
*
If you do not want all requests to go to the parent cache, you can configure the proxy to route certain requests directly to the origin server (for example, requests that contain specific URLs) by setting parent proxy rules in the parent.config configuration file (described in parent.config).
*
If the request is a cache miss on the parent, the parent retrieves the content from the origin server (or from another cache, depending on the parent's configuration). The parent caches the content and then sends a copy to the proxy (its child), where it is cached and served to the client.
Parent failover
When you configure the proxy to use more than one parent cache, the proxy detects when a parent is not available and sends missed requests to another parent cache. If you specify more than two parent caches, the order in which the parent caches are queried depends upon the parent proxy rules configured in the parent configuration file described in parent.config. By default, the parent caches are queried in the order in which they are listed in the configuration file.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Hierarchical Caching > HTTP cache hierarchies
Copyright 2017 Forcepoint. All rights reserved.