HTTP caching for https://remix.run

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: max-age=300, stale-while-revalidate=604800
❌

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: 353
cache-control: max-age=300, stale-while-revalidate=604800
🧭

Cache-Control

Cache-Control: max-age=300, stale-while-revalidate=604800
  • ⏳
    Max Age
    (RFC)

    The max-age directive indicates the response should be considered stale after 300 seconds (5 minutes).

    For example, since this response was fetched on Jun 19, 2026, 6:53:06 PM, it will become stale on Jun 19, 2026, 6:58:06 PM.

  • 🔁
    Stale While Revalidate
    (RFC)
    The stale-while-revalidate directive indicates that after a response becomes stale, the cache may continue to serve it for up to 604800 seconds (7 days) while it is revalidated in the background.
⌛

Age

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

Age: 353

In this case, the response has been in the cache for 353 seconds (5 minutes 53 seconds).