Configuring caching policies - Platform - BlueCat Gateway - 20.12.1

Gateway Administration Guide

prodname
BlueCat Gateway
version_custom
20.12.1

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:

  1. Log in to BlueCat Gateway.
  2. Select Administration > Configurations > General Configuration.
  3. Click Security.


  4. Click the No Store checkbox. The no-store cacheability directive specifies that the response may not be stored in any cache.
  5. 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.
  6. Specify the maximum amount of time in seconds that a resource is considered fresh on the Max Age (seconds) field. The default value is 86400 seconds (or one day).
  7. 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.
  8. 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.
  9. Click the Pragma checkbox for allowing backwards compatibility with HTTP/1.0 clients.
  10. Click Save.
    Related links: