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=135
This resource does not have an entity tag.
cache-control: max-age=135 expires: Fri, 01 Nov 2024 22:14:04 GMT vary: Accept-Encoding
Cache-Control: max-age=135
The max-age
directive indicates the response should be considered stale after 135 seconds (2 minutes 15 seconds).
For example, since this response was fetched on Nov 1, 2024, 10:11:49 PM, it will become stale on Nov 1, 2024, 10:14:04 PM.
⚠️ The Expires
header is redundant with the max-age
directive in the Cache-Control
header, so the Expires
header will be ignored.
The Expires
header indicates the time at which the response will expire.
Expires: Fri, 01 Nov 2024 22:14:04 GMT
In this case, the response will expire on Nov 1, 2024, 10:14:04 PM (in 2 minutes).
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.