Class CacheConfig
- All Implemented Interfaces:
Cloneable
Configuration for HTTP caches
Cache configuration can be grouped into the following categories:
Protocol options. I some cases the HTTP protocol allows for
conditional behaviors or optional protocol extensions. Such conditional
protocol behaviors or extensions can be turned on or off here.
See isNeverCacheHTTP10ResponsesWithQuery(),
isNeverCacheHTTP11ResponsesWithQuery(),
isStaleIfErrorEnabled()
Cache size. If the backend storage supports these limits, one
can specify the maximum number of
cache entries as well as the getMaxObjectSize()
maximum cacheable response body size}.
Public/private caching. By default, the caching module considers
itself to be a shared (public) cache, and will not, for example, cache
responses to requests with Authorization headers or responses
marked with Cache-Control: private. If, however, the cache
is only going to be used by one logical "user" (behaving similarly to a
browser cache), then one may want to isSharedCache()
turn off the shared cache setting}.
Heuristic caching. Per HTTP caching specification, a cache may
cache certain cache entries even if no explicit cache control headers are
set by the origin. This behavior is off by default, but you may want to
turn this on if you are working with an origin that doesn't set proper
headers but where one may still want to cache the responses. Use isHeuristicCachingEnabled() to enable heuristic caching},
then specify either a default freshness lifetime and/or a fraction of the time since
the resource was last modified.
Background validation. The cache module supports the
stale-while-revalidate directive, which allows certain cache entry
revalidations to happen in the background. Asynchronous validation is enabled
by default but it could be disabled by setting the number of re-validation
workers to 0 with getAsynchronousWorkers()
parameter
-
Nested Class Summary
Nested Classes -
Field Summary
FieldsModifier and TypeFieldDescriptionprivate final intstatic final CacheConfigstatic final booleanDeprecated.No longer applicable.static final intDefault number of worker threads to allow for background revalidations resulting from the stale-while-revalidate directive.static final booleanDefault setting for heuristic cachingstatic final floatDefault coefficient used to heuristically determine freshness lifetime from the Last-Modified time of a cache entry.static final org.apache.hc.core5.util.TimeValueDefault lifetime to be assumed when we cannot calculate freshness heuristically.static final intDefault setting for the maximum number of cache entries that will be retained.static final intDefault setting for the maximum object size that will be cached, in bytes.static final intDefault setting for the number of retries on a failed cache processChallengestatic final booleanDeprecated.No longer applicable.private final booleanprivate final booleanprivate final floatprivate final org.apache.hc.core5.util.TimeValueprivate final intprivate final longprivate final intprivate final booleanprivate final booleanA constant indicating whether HTTP/1.1 responses with a query string should never be cached.private final booleanprivate final boolean -
Constructor Summary
ConstructorsConstructorDescriptionCacheConfig(long maxObjectSize, int maxCacheEntries, int maxUpdateRetries, boolean heuristicCachingEnabled, float heuristicCoefficient, org.apache.hc.core5.util.TimeValue heuristicDefaultLifetime, boolean sharedCache, boolean freshnessCheckEnabled, int asynchronousWorkers, boolean neverCacheHTTP10ResponsesWithQuery, boolean neverCacheHTTP11ResponsesWithQuery, boolean staleIfErrorEnabled) -
Method Summary
Modifier and TypeMethodDescriptionprotected CacheConfigclone()static CacheConfig.Buildercopy(CacheConfig config) static CacheConfig.Buildercustom()intReturns the maximum number of threads to allow for background revalidations due to thestale-while-revalidatedirective.floatReturns lifetime coefficient used in heuristic freshness caching.org.apache.hc.core5.util.TimeValueGet the default lifetime to be used if heuristic freshness calculation is not possible.intReturns the maximum number of cache entries the cache will retain.longReturns the current maximum response body size that will be cached.intReturns the number of times to retry a cache processChallenge on failurebooleanDeprecated.No longer applicable.booleanReturns whether the cache will perform an extra cache entry freshness check upon cache update in case of a cache missbooleanReturns whether heuristic caching is enabled.booleanReturns whether the cache will never cache HTTP 1.0 responses with a query string or not.booleanDetermines whether HTTP/1.1 responses with query strings should never be cached by the client.booleanReturns whether the cache will behave as a shared cache or not.booleanReturns a boolean value indicating whether the stale-if-error cache directive is enabled.booleanDeprecated.Do not use.toString()
-
Field Details
-
DEFAULT_MAX_OBJECT_SIZE_BYTES
public static final int DEFAULT_MAX_OBJECT_SIZE_BYTESDefault setting for the maximum object size that will be cached, in bytes.- See Also:
-
DEFAULT_MAX_CACHE_ENTRIES
public static final int DEFAULT_MAX_CACHE_ENTRIESDefault setting for the maximum number of cache entries that will be retained.- See Also:
-
DEFAULT_MAX_UPDATE_RETRIES
public static final int DEFAULT_MAX_UPDATE_RETRIESDefault setting for the number of retries on a failed cache processChallenge- See Also:
-
DEFAULT_303_CACHING_ENABLED
Deprecated.No longer applicable. Do not use.- See Also:
-
DEFAULT_WEAK_ETAG_ON_PUTDELETE_ALLOWED
Deprecated.No longer applicable. Do not use.- See Also:
-
DEFAULT_HEURISTIC_CACHING_ENABLED
public static final boolean DEFAULT_HEURISTIC_CACHING_ENABLEDDefault setting for heuristic caching- See Also:
-
DEFAULT_HEURISTIC_COEFFICIENT
public static final float DEFAULT_HEURISTIC_COEFFICIENTDefault coefficient used to heuristically determine freshness lifetime from the Last-Modified time of a cache entry.- See Also:
-
DEFAULT_HEURISTIC_LIFETIME
public static final org.apache.hc.core5.util.TimeValue DEFAULT_HEURISTIC_LIFETIMEDefault lifetime to be assumed when we cannot calculate freshness heuristically. -
DEFAULT_ASYNCHRONOUS_WORKERS
public static final int DEFAULT_ASYNCHRONOUS_WORKERSDefault number of worker threads to allow for background revalidations resulting from the stale-while-revalidate directive.- See Also:
-
DEFAULT
-
maxObjectSize
private final long maxObjectSize -
maxCacheEntries
private final int maxCacheEntries -
maxUpdateRetries
private final int maxUpdateRetries -
heuristicCachingEnabled
private final boolean heuristicCachingEnabled -
heuristicCoefficient
private final float heuristicCoefficient -
heuristicDefaultLifetime
private final org.apache.hc.core5.util.TimeValue heuristicDefaultLifetime -
freshnessCheckEnabled
private final boolean freshnessCheckEnabled -
asynchronousWorkers
private final int asynchronousWorkers -
neverCacheHTTP10ResponsesWithQuery
private final boolean neverCacheHTTP10ResponsesWithQuery -
staleIfErrorEnabled
private final boolean staleIfErrorEnabled -
neverCacheHTTP11ResponsesWithQuery
private final boolean neverCacheHTTP11ResponsesWithQueryA constant indicating whether HTTP/1.1 responses with a query string should never be cached.
-
-
Constructor Details
-
CacheConfig
CacheConfig(long maxObjectSize, int maxCacheEntries, int maxUpdateRetries, boolean heuristicCachingEnabled, float heuristicCoefficient, org.apache.hc.core5.util.TimeValue heuristicDefaultLifetime, boolean sharedCache, boolean freshnessCheckEnabled, int asynchronousWorkers, boolean neverCacheHTTP10ResponsesWithQuery, boolean neverCacheHTTP11ResponsesWithQuery, boolean staleIfErrorEnabled)
-
-
Method Details
-
getMaxObjectSize
public long getMaxObjectSize()Returns the current maximum response body size that will be cached.- Returns:
- size in bytes
- Since:
- 4.2
-
isNeverCacheHTTP10ResponsesWithQuery
public boolean isNeverCacheHTTP10ResponsesWithQuery()Returns whether the cache will never cache HTTP 1.0 responses with a query string or not.- Returns:
trueto not cache query string responses,falseto cache if explicit cache headers are found
-
isNeverCacheHTTP11ResponsesWithQuery
public boolean isNeverCacheHTTP11ResponsesWithQuery()Determines whether HTTP/1.1 responses with query strings should never be cached by the client. By default, caching of such responses is allowed. Enabling this option may improve security by preventing responses with sensitive information from being cached.Note that this option only applies to HTTP/1.1.
- Returns:
trueif HTTP/1.1 responses with query strings should never be cached;falseotherwise.- Since:
- 5.4
-
isStaleIfErrorEnabled
public boolean isStaleIfErrorEnabled()Returns a boolean value indicating whether the stale-if-error cache directive is enabled. If this option is enabled, cached responses that have become stale due to an error (such as a server error or a network failure) will be returned instead of generating a new request. This can help to reduce the load on the origin server and improve performance.- Returns:
trueif the stale-if-error directive is enabled, orfalseotherwise.
-
getMaxCacheEntries
public int getMaxCacheEntries()Returns the maximum number of cache entries the cache will retain. -
getMaxUpdateRetries
public int getMaxUpdateRetries()Returns the number of times to retry a cache processChallenge on failure -
is303CachingEnabled
Deprecated.No longer applicable. Do not use. -
isWeakETagOnPutDeleteAllowed
Deprecated.Do not use.Returns whether weak etags is allowed with PUT/DELETE methods.- Returns:
trueif it is allowed.
-
isHeuristicCachingEnabled
public boolean isHeuristicCachingEnabled()Returns whether heuristic caching is enabled.- Returns:
trueif it is enabled.
-
getHeuristicCoefficient
public float getHeuristicCoefficient()Returns lifetime coefficient used in heuristic freshness caching. -
getHeuristicDefaultLifetime
public org.apache.hc.core5.util.TimeValue getHeuristicDefaultLifetime()Get the default lifetime to be used if heuristic freshness calculation is not possible. -
isFreshnessCheckEnabled
public boolean isFreshnessCheckEnabled()Returns whether the cache will perform an extra cache entry freshness check upon cache update in case of a cache miss- Since:
- 5.0
-
getAsynchronousWorkers
public int getAsynchronousWorkers()Returns the maximum number of threads to allow for background revalidations due to thestale-while-revalidatedirective. A value of 0 means background revalidations are disabled. -
clone
- Overrides:
clonein classObject- Throws:
CloneNotSupportedException
-
custom
-
copy
-
toString
-