Http Caches

HTTP clients may cache responses if configured with a cache.

Responses are only cached when the origin server explicitly sends the appropriate headers (heuristics caching is not currently supported).

Getting Started#

To configure an HTTP Cache in the Admin UI, navigate to Facilities → HTTP Caches. From there you can create a new, or edit the existing HTTP Caches.

Create HTTP Cache
Create HTTP Cache. (Admin UI version: 10.6)

Types#

The following HTTP Cache types are supported:

  • in-memory (per node).
  • Bucket (shared across nodes) (See Data Sources for information about Buckets).

Cache Configuration#

Max Entries#

The Bucket HTTP Cache Type does not support this setting.

Defines the maximum number of entries the cache may hold.

Default: 1024

Max Object Size#

Defines the maximum size (in KiB) of an object that may be cached.

Default: 1024

Shared#

Whether the cache is shared between users.

Default: true

If a Cache-Control response header has the private directive, the client will only use the cache if this setting is set to false. In such case, extreme care must be taken to only use the cache for HTTP Clients that use the same user credentials or API key.

Was this helpful?