HTTP caching for https://apple.com

Overview

❌

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 has a cache control header.

Cache-Control: max-age=0
❌

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: max-age=0
expires: Tue, 01 Apr 2025 17:06:41 GMT
vary: Accept-Encoding
🧭

Cache-Control

Cache-Control: max-age=0
  • ⏳
    Max Age
    (RFC)

    The max-age directive indicates the response should be considered stale immediately.

    For example, since this response was fetched on Apr 1, 2025, 5:06:41 PM, it will become stale on Apr 1, 2025, 5:06:41 PM.

🗑️

Expires

The Expires header indicates the time at which the response will expire.

Expires: Tue, 01 Apr 2025 17:06:41 GMT

In this case, the time is in the past, which means the response should be considered stale immediately.

🔀

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.