Configuring caching policies - Platform - BlueCat Gateway - 25.3.0

Gateway Administration Guide

ft:locale
en-US
Product name
BlueCat Gateway
Version
25.3.0

Within Security settings in the General Configuration page, you can configure caching headers to control how browsers cache data when using Gateway.

You can manage the following HTTP caching headers:

To specify the cache control header details for Gateway:

  1. Open the General configuration window, then expand the Security section. (Click Settings at the bottom of the navigator on the left, expand Configurations, then click General configuration. Click Security to scroll to the Security section.)

  2. Scroll down to the Cache control and Cache storage sections, then fill in the settings as needed

    For more details, see Cache control and Cache storage settings list below.

  3. When you're done, click Save changes.

    To cancel your changes, click Cancel.

Cache control and Cache storage settings list

The Interface section has the following settings.

Setting Description
Don't cache response (no-store)

If ticked, specifies that responses must not be stored in any cache.

Revalidate response before each reuse cache (no-cache)

Specifies 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.

Max age (seconds)

Specifies the maximum amount of time in seconds that a resource is considered "fresh". The default is 86400 seconds (one day).

Cache storage Specifies the storage type where the response can be stored. You can choose from the following:
  • Public: The response may be stored in any cache.
  • Private: The the response may be stored only by a browser's cache.
Max revalidate

If ticked, specifies 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.

Pragma If ticked, allows for backwards compatibility with HTTP/1.0 clients.