HTTP caching for https://cachecheck.net/examples/max-age

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: no-transform, max-age=3600, s-maxage=7200
❌

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:
cache-control: no-transform, max-age=3600, s-maxage=7200
🧭

Cache-Control

Cache-Control: no-transform, max-age=3600, s-maxage=7200
  • ⏳
    Max Age
    (RFC)

    The max-age directive indicates the response should be considered stale after 3600 seconds (1 hour).

    For example, since this response was fetched on May 17, 2024, 11:30:39 AM, it will become stale on May 17, 2024, 12:30:39 PM.

  • ⌛
    Shared Max Age
    (RFC)

    The s-maxage directive indicates the response should be considered stale by shared caches (such as a CDN) after 7200 seconds (2 hours).

    For example, since this response was fetched on May 17, 2024, 11:30:39 AM, it will become stale for shared caches on May 17, 2024, 1:30:39 PM.

  • ✨
    No Transform
    (RFC)
    The no-transform directive indicates that any intermediate cache must not transform this response (for example: change content type, compress data, filter responses, etc.)