Support
|
|
|
|
|
Web Proxy Caching > Caching HTTP objects > Client directives > 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.
|
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.
|
|
1.
|
Navigate to Configure > Protocols > HTTP > Cacheability.
|
|
2.
|
|
3.
|
Click Apply.
|
|
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 Content Gateway Manager (in the Behavior section Configure > Protocols > HTTP > Cacheability tab).
|
Quick Links
Service Requests
How are we doing?
Provide us feedback on your experience with the Service Request portal.
provide feedback >|
|
|
|
|
|
Web Proxy Caching > Caching HTTP objects > Client directives > Configuring the proxy to ignore client no-cache headers
|
