This resource can be cached.
This response can be cached because of a directive in the Cache-Control
header.
This resource has a cache control header.
Cache-Control: no-transform, max-age=3600, s-maxage=7200, stale-while-revalidate=36000
This resource does not have an entity tag.
cache-control: no-transform, max-age=3600, s-maxage=7200, stale-while-revalidate=36000
Cache-Control: no-transform, max-age=3600, s-maxage=7200, stale-while-revalidate=36000
The max-age
directive indicates the response should be considered stale after 3600 seconds (1 hour).
For example, since this response was fetched on Nov 1, 2024, 10:56:42 PM, it will become stale on Nov 1, 2024, 11:56:42 PM.
The s-maxage
directive indicates the response should be considered stale by shared caches (such as a CDN) after 7200 seconds (2 hours).
For example, since this response was fetched on Nov 1, 2024, 10:56:42 PM, it will become stale for shared caches on Nov 2, 2024, 12:56:42 AM.
no-transform
directive indicates that any intermediate cache must not transform this response (for example: change content type, compress data, filter responses, etc.)stale-while-revalidate
directive indicates that after a response becomes stale, the cache may continue to serve it for up to 36000 seconds (10 hours) while it is revalidated in the background.