Enabling Custom Cache Control Headers - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

Use a Cache-Control: Private header to prevent external caches from caching the object at all.
Use a custom cache control header, such as MYCACHE: 1800, to indicate that the proxy
service should cache the object for 30 minutes.
Custom Cache Control Headers override the following standard HTTP cache-control headers on the
Access Gateway, but they do not affect how browsers and external caches respond to them:
Cache-Control: no-store
Cache-Control: no-cache
Cache-Control: max-age=number
Cache-Control: private
Cache-Control: public
Pragma: no-cache
Expires: date

5.3.2 Enabling Custom Cache Control Headers

1 In the Administration Console, click Devices > Access Gateways > Edit > [Name of Reverse
Proxy] > [Name of Proxy Service] > HTTP Options.
2 To enable the use of custom headers, select Enable Custom Cache Control Header.
With this option selected, the proxy service searches HTTP packets for custom cache control
headers, and caches the objects according to its policies. The policy contains a timer, which
specifies how long the object can be cached before checking with the Web server for updates.
3 Select one of the following options to specify what occurs when the custom cache control
expiration time expires.
Revalidate the object with a "Get-If-Modified": Causes the proxy service to update the
object in cache only if the object has been modified.
Always obtain a fresh copy of the object: Causes the proxy service to update the object
in cache, even if the object has not been modified.
4 In the Cache Control Header List, select New and specify a name for the header, for example
MYCACHE.
5 To save your changes to browser cache, click OK.
6 To apply the changes, click the Access Gateways link, then click Update > OK.
174 Novell Access Manager 3.1 SP2 Access Gateway Guide