Technical Library
|
Support
Hierarchical Caching
> HTTP cache hierarchies
HTTP cache hierarchies
Help | Content Gateway | Version 8.0.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.
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 in
Parent failover
.
Note
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
).
Note
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.
Hierarchical Caching
> HTTP cache hierarchies
Copyright 2016 Forcepoint LLC. All rights reserved.