Specify the caching headers for BlueCat Gateway.
- Cache-Control: The HTTP header that holds directives (instructions) for caching in both requests and responses.
- Pragma: The HTTP/1.0 general header that is used for backwards compatibility with HTTP/1.0 caches where the Cache-Control HTTP/1.1 is not yet present.
- For more information on Cache-Control, refer to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
- For more information on Pragma, refer to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Pragma
To specify the Cache-Control and Pragma headers for BlueCat Gateway:
-
Log in to BlueCat Gateway.
-
Select .
-
Click Security.
- In the Cache Control section, configure the following.
-
Select the No Store checkbox to specify that the response must not be stored in any cache.
-
Select the 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 value is 86400 seconds (one day).
-
In the Public/Private drop-down menu, select the cacheability directive that specifies 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.