HTTP caching for https://camchenry.com

Overview

✅

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: public, max-age=21600
❌

This resource does not have an entity tag.

HTTP response cache headers

These are the raw caching-related HTTP headers that were returned by the server:
age: 0
cache-control: public, max-age=21600
vary: accept-encoding
🧭

Cache-Control

Cache-Control: public, max-age=21600
  • 🌐
    Public
    (RFC)
    The public directive indicates that any cache may cache the response, even if it would not typically be cacheable.
  • ⏳
    Max Age
    (RFC)

    The max-age directive indicates the response should be considered stale after 21600 seconds (6 hours).

    For example, since this response was fetched on Apr 4, 2025, 2:10:33 AM, it will become stale on Apr 4, 2025, 8:10:33 AM.

⌛

Age

The Age header indicates how long the response has been in the cache.

Age: 0

In this case, the age is zero, which means the response was likely fetched from the origin server and has not been cached yet.

🔀

Vary

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.