Configuring the proxy to ignore client no-cache headers

By default, Content Gateway observes client Cache Control:no-cache directives. If a requested object contains a no-cache header, the proxy forwards the request to the origin server even if it has a fresh copy in the cache.

You can configure the proxy to ignore client no-cache directives. In this case, the proxy ignores no-cache headers from client requests and serves the object from its cache.


	Important The default behavior of observing no-cache directives is appropriate in most cases. Configure Content Gateway to ignore client no-cache directives only if you are knowledgeable about HTTP 1.1.

Navigate to Configure > Protocols > HTTP > Cacheability.

In the Behavior section, enable the Ignore "no-cache" in Client Requests option.

Click Apply.


	Note Certain versions of Microsoft Internet Explorer do not request cache reloads from transparent caches when the user presses the browser Refresh button. This can prevent content from being loaded directly from the origin server. You can configure Content Gateway to treat Microsoft Internet Explorer requests more conservatively, providing fresher content at the cost of serving fewer documents from the cache. You can configure the proxy to add no-cache headers to requests from Microsoft Internet Explorer in the Content Gateway manager (in the Behavior section of the Configure > Protocols > HTTP > Cacheability tab).