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.
Type#
Currently, only in-memory (per node) cache is supported.
Max Entries#
Defines the maximum number of entries the cache may hold.
Max Object Size#
Defines the maximum size (in KiB) of an object that may be cached.
Shared#
Defines whether the cache is shared between multiple users.
Used by HTTP Clients#
Allows to select which HTTP clients will use this cache.