Class CacheControl
Adding Cache-Control directives to HTTP responses can significantly improve the client experience when interacting with a web application. This builder creates opinionated "Cache-Control" headers with response directives only, with several use cases in mind.
- Caching HTTP responses with
CacheControl cc = CacheControl.maxAge(1, TimeUnit.HOURS)
will result inCache-Control: "max-age=3600"
- Preventing cache with
CacheControl cc = CacheControl.noStore()
will result inCache-Control: "no-store"
- Advanced cases like
CacheControl cc = CacheControl.maxAge(1, TimeUnit.HOURS).noTransform().cachePublic()
will result inCache-Control: "max-age=3600, no-transform, public"
Note that to be efficient, Cache-Control headers should be written along HTTP validators such as "Last-Modified" or "ETag" headers.
- Since:
- 4.2
- Author:
- Brian Clozel, Juergen Hoeller
- See Also:
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionAdd a "private" directive.Add a "public" directive.static CacheControl
empty()
Return an empty directive.Return the "Cache-Control" header value, if any.static CacheControl
Add a "max-age=" directive.static CacheControl
Add a "max-age=" directive.Add a "must-revalidate" directive.static CacheControl
noCache()
Add a "no-cache" directive.static CacheControl
noStore()
Add a "no-store" directive.Add a "no-transform" directive.Add a "proxy-revalidate" directive.Add an "s-maxage" directive.Add an "s-maxage" directive.staleIfError
(long staleIfError, TimeUnit unit) Add a "stale-if-error" directive.staleIfError
(Duration staleIfError) Add a "stale-if-error" directive.staleWhileRevalidate
(long staleWhileRevalidate, TimeUnit unit) Add a "stale-while-revalidate" directive.staleWhileRevalidate
(Duration staleWhileRevalidate) Add a "stale-while-revalidate" directive.toString()
-
Constructor Details
-
CacheControl
protected CacheControl()Create an empty CacheControl instance.- See Also:
-
-
Method Details
-
empty
Return an empty directive.This is well suited for using other optional directives without "max-age", "no-cache" or "no-store".
- Returns:
this
, to facilitate method chaining
-
maxAge
Add a "max-age=" directive.This directive is well suited for publicly caching resources, knowing that they won't change within the configured amount of time. Additional directives can be also used, in case resources shouldn't be cached (
cachePrivate()
) or transformed (noTransform()
) by shared caches.In order to prevent caches to reuse the cached response even when it has become stale (i.e. the "max-age" delay is passed), the "must-revalidate" directive should be set (
mustRevalidate()
- Parameters:
maxAge
- the maximum time the response should be cachedunit
- the time unit of themaxAge
argument- Returns:
this
, to facilitate method chaining- See Also:
-
maxAge
Add a "max-age=" directive.This directive is well suited for publicly caching resources, knowing that they won't change within the configured amount of time. Additional directives can be also used, in case resources shouldn't be cached (
cachePrivate()
) or transformed (noTransform()
) by shared caches.In order to prevent caches to reuse the cached response even when it has become stale (i.e. the "max-age" delay is passed), the "must-revalidate" directive should be set (
mustRevalidate()
- Parameters:
maxAge
- the maximum time the response should be cached- Returns:
this
, to facilitate method chaining- Since:
- 5.2
- See Also:
-
noCache
Add a "no-cache" directive.This directive is well suited for telling caches that the response can be reused only if the client revalidates it with the server. This directive won't disable cache altogether and may result with clients sending conditional requests (with "ETag", "If-Modified-Since" headers) and the server responding with "304 - Not Modified" status.
In order to disable caching and minimize requests/responses exchanges, the
noStore()
directive should be used instead of#noCache()
.- Returns:
this
, to facilitate method chaining- See Also:
-
noStore
Add a "no-store" directive.This directive is well suited for preventing caches (browsers and proxies) to cache the content of responses.
- Returns:
this
, to facilitate method chaining- See Also:
-
mustRevalidate
Add a "must-revalidate" directive.This directive indicates that once it has become stale, a cache MUST NOT use the response to satisfy subsequent requests without successful validation on the origin server.
- Returns:
this
, to facilitate method chaining- See Also:
-
noTransform
Add a "no-transform" directive.This directive indicates that intermediaries (caches and others) should not transform the response content. This can be useful to force caches and CDNs not to automatically gzip or optimize the response content.
- Returns:
this
, to facilitate method chaining- See Also:
-
cachePublic
Add a "public" directive.This directive indicates that any cache MAY store the response, even if the response would normally be non-cacheable or cacheable only within a private cache.
- Returns:
this
, to facilitate method chaining- See Also:
-
cachePrivate
Add a "private" directive.This directive indicates that the response message is intended for a single user and MUST NOT be stored by a shared cache.
- Returns:
this
, to facilitate method chaining- See Also:
-
proxyRevalidate
Add a "proxy-revalidate" directive.This directive has the same meaning as the "must-revalidate" directive, except that it does not apply to private caches (i.e. browsers, HTTP clients).
- Returns:
this
, to facilitate method chaining- See Also:
-
sMaxAge
Add an "s-maxage" directive.This directive indicates that, in shared caches, the maximum age specified by this directive overrides the maximum age specified by other directives.
- Parameters:
sMaxAge
- the maximum time the response should be cachedunit
- the time unit of thesMaxAge
argument- Returns:
this
, to facilitate method chaining- See Also:
-
sMaxAge
Add an "s-maxage" directive.This directive indicates that, in shared caches, the maximum age specified by this directive overrides the maximum age specified by other directives.
- Parameters:
sMaxAge
- the maximum time the response should be cached- Returns:
this
, to facilitate method chaining- Since:
- 5.2
- See Also:
-
staleWhileRevalidate
Add a "stale-while-revalidate" directive.This directive indicates that caches MAY serve the response in which it appears after it becomes stale, up to the indicated number of seconds. If a cached response is served stale due to the presence of this extension, the cache SHOULD attempt to revalidate it while still serving stale responses (i.e. without blocking).
- Parameters:
staleWhileRevalidate
- the maximum time the response should be used while being revalidatedunit
- the time unit of thestaleWhileRevalidate
argument- Returns:
this
, to facilitate method chaining- See Also:
-
staleWhileRevalidate
Add a "stale-while-revalidate" directive.This directive indicates that caches MAY serve the response in which it appears after it becomes stale, up to the indicated number of seconds. If a cached response is served stale due to the presence of this extension, the cache SHOULD attempt to revalidate it while still serving stale responses (i.e. without blocking).
- Parameters:
staleWhileRevalidate
- the maximum time the response should be used while being revalidated- Returns:
this
, to facilitate method chaining- Since:
- 5.2
- See Also:
-
staleIfError
Add a "stale-if-error" directive.This directive indicates that when an error is encountered, a cached stale response MAY be used to satisfy the request, regardless of other freshness information.
- Parameters:
staleIfError
- the maximum time the response should be used when errors are encounteredunit
- the time unit of thestaleIfError
argument- Returns:
this
, to facilitate method chaining- See Also:
-
staleIfError
Add a "stale-if-error" directive.This directive indicates that when an error is encountered, a cached stale response MAY be used to satisfy the request, regardless of other freshness information.
- Parameters:
staleIfError
- the maximum time the response should be used when errors are encountered- Returns:
this
, to facilitate method chaining- Since:
- 5.2
- See Also:
-
getHeaderValue
Return the "Cache-Control" header value, if any.- Returns:
- the header value, or
null
if no directive was added
-
toString
-