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.
Follow the steps below to specify the Cache-Control and Pragma headers for BlueCat Gateway:
- Log in to BlueCat Gateway.
- Select .
- Click the No Store checkbox. The no-store cacheability directive specifies that the response may not be stored in any cache.
- Click the No Cache checkbox. The no-cache cacheability directive specifies that the response may be stored by any cache, even if the response is generally non-cacheable.
Specify the maximum amount of time in seconds that a resource is considered
fresh on the Max Age (seconds) field. The default value
86400seconds (or one day).
- Select public or private from the Public/Private drop-down menu. The public cacheability directive specifies that the response may be stored in any cache, whereas the private cacheability directive specifies that the response may be stored only by a browser's cache.
- Click the Must Revalidate checkbox. The must-revalidate directive indicates that once a resource becomes stale, caches must not use their stale copy without successful validation on the origin server.
- Click the Pragma checkbox for allowing backwards compatibility with HTTP/1.0 clients.
- 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