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: max-age=300, stale-while-revalidate=604800
This resource does not have an entity tag.
age: 1029 cache-control: max-age=300, stale-while-revalidate=604800 vary: Accept-Encoding
Cache-Control: max-age=300, stale-while-revalidate=604800
The max-age
directive indicates the response should be considered stale after 300 seconds (5 minutes).
For example, since this response was fetched on Nov 1, 2024, 11:32:16 PM, it will become stale on Nov 1, 2024, 11:37:16 PM.
stale-while-revalidate
directive indicates that after a response becomes stale, the cache may continue to serve it for up to 604800 seconds (7 days) while it is revalidated in the background.The Age
header indicates how long the response has been in the cache.
Age: 1029
In this case, the response has been in the cache for 1029 seconds (17 minutes 9 seconds).
The Vary
header indicates which request headers the server response may be dependent on. If any of the listed headers change, then the response may be different. This allows the server to send the correct cached response for each request. For example, ensuring that a client that does not support compression does not receive a cached compressed response.
Vary: Accept-Encoding
Accept-Encoding: The server response is expected to be different depending on the encodings that the client accepts via the Accept-Encoding
header in the request. For example, if the client does not support compression, then the server may send a cached uncompressed response. If the client does support compression, for example, by sending a a Accept-Encoding: gzip
header, then the server may send a cached compressed response.