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: 534
cache-control: max-age=300, stale-while-revalidate=604800
vary: Cookie, Accept-Encoding
🧭

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 May 17, 2024, 10:38:28 AM, it will become stale on May 17, 2024, 10:43:28 AM.

  • 🔁
    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: 534

In this case, the response has been in the cache for 534 seconds (8 minutes 54 seconds).

🔀

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: Cookie, 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.

Cookie: The server response will depend on the cookies that the client sends in the request. Typically, this means that the server will cache authenticated responses (since authenticated responses typically include a cookie), but the cached pages will only be served to the same client that sent the request.