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-cache
This resource does not have an entity tag.
cache-control: no-cache vary: Accept-Encoding
Cache-Control: no-cache
no-cache
directive indicates that this response may be cached, but any cached response must be validated with the origin server before it can be used.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.