Cache-Control

Select directives to construct a Cache-Control header.

cache-control: max-age=3600, must-revalidate, public

The response can be stored by the client, CDN, and any intermediary caches. The cached response must be validated by the client before each use, even if fresh. The response can be cached for a maximum of 1 hour, as specified by the origin server.

    Directives

    The maximum amount of time a resource is considered fresh.

    The browser or CDN can store the response but must revalidate with the origin before serving it.

    The browser, CDN, and server are disallowed from storing any version of the returned response.

    The browser, CDN, or any intermediary must not transform the payload of the response.

    Similar to max-age but applies only to shared caches (CDN).

    Once a resource becomes stale, caches (browser or CDN) must not use their stale copy without successful validation with the server.

    Similar to must-revalidate but does not apply to private user agent caches (browser).

    The response is intended only for a single user (browser) and must not be stored by a shared cache (CDN).

    The response may be stored by any cache including the browser and CDN.

    The browser or CDN can serve a stale response while it revalidates in the background.

    The browser or CDN can serve a stale response if the server is unavailable.