This resource might not be cached.
This response might not be cached because the server did not respond with any valid caching headers such as Cache-Control or ETag. It may still be cached, but there were no explicit directives on how to handle caching for intermediate caches or the browser.
This resource does not have a cache control header.
Learn how to add the Cache-Control header to your responses.
This resource does not have an entity tag.
vary: Content-Type,Accept-Encoding,User-Agent
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: Content-Type,Accept-Encoding,User-Agent
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.
User-Agent: The server response will depend on the user agent that the client sends in the request. Typically, this means that the server will cache responses for different browsers, operating systems, or devices.