Within Security settings in the General Configuration, you can configure caching headers to control how browsers cache data when using Gateway.
Cache-control: Holds directives (instructions) for caching in both requests and responses.
For more details, see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control on the Mozilla website.
Pragma: An HTTP/1.0 general header for backwards compatibility with HTTP/1.0 caches where Cache-Control HTTP/1.1 is not yet present.
For more details, see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Pragma on the Mozilla website.
To specify the cache control header details for Gateway:
-
Open the General configuration window, then expand the Security section. (Click the
Navigator
button if necessary, then click . Click Security at the bottom to expand
the Security settings.) - Scroll down to the Cache control section, then configure the
following.
-
Select the Don't cache response (no-store) checkbox to specify that the response must not be stored in any cache.
-
Select the Revalidate response before each reuse cache (no-cache) checkbox to specify that the response may be stored in any cache, even if the response is generally non-cacheable. Doing so enables the no-cache cacheability directive.
-
In Max age (seconds), specify the maximum amount of time in seconds that a resource is considered "fresh". The default is
86400seconds (one day). -
In the Cache storage, select where the response can be stored:
- Public: The response may be stored in any cache.
- Private: The the response may be stored only by a browser's cache.
-
Select the Must revalidate checkbox to specify that caches must not use stale copies of a resource without successfully validating it from the origin server. Doing so enables the must-revalidate directive.
-
Select the Pragma checkbox to allow for backwards compatibility with HTTP/1.0 clients.
-
When you're done, click Save.
To cancel your changes, click Cancel.