CacheControl

The immutable response directive indicates that the response will not be updated while it's fresh

The max-age=N response directive indicates that the response remains fresh until N seconds after the response is generated.

The max-age=N request directive indicates that the client allows a stored response that is generated on the origin server within N seconds

The max-stale=N request directive indicates that the client allows a stored response that is stale within N seconds.

The min-fresh=N request directive indicates that the client allows a stored response that is fresh for at least N seconds.

Maintains a chunk of CacheControl values.

The must-revalidate response directive indicates that the response can be stored in caches and can be reused while fresh. If the response becomes stale, it must be validated with the origin server before reuse.

The must-understand response directive indicates that a cache should store the response only if it understands the requirements for caching based on status code.

The no-cache response directive indicates that the response can be stored in caches, but the response must be validated with the origin server before each reuse.

The no-cache request directive asks caches to validate the response with the origin server before reuse.

The no-store response directive indicates that any caches of any kind (private or shared) should not store this response.

The no-store request directive allows a client to request that caches refrain from storing the request and corresponding response — even if the origin server's response could be stored.

The no-transform indicates that any intermediary (regardless of whether it implements a cache) shouldn't transform the response/request contents.

The client indicates that cache should obtain an already-cached response. If a cache has stored a response, it's reused.

The private response directive indicates that the response can be stored only in a private cache

The proxy-revalidate response directive is the equivalent of must-revalidate, but specifically for shared caches only.

The public response directive indicates that the response can be stored in a shared cache.

The s-maxage response directive also indicates how long the response is fresh for (similar to max-age) — but it is specific to shared caches, and they will ignore max-age when it is present.

The stale-if-error response directive indicates that the cache can reuse a stale response when an origin server responds with an error (500, 502, 503, or 504).

The stale-while-revalidate response directive indicates that the cache could reuse a stale response while it revalidates it to a cache.

The names of the product elements

The name of the type