HTTP caching for https://youtube.com

Overview

❌

This resource might not be cached.

This response cannot be cached because the server responded with no-store in the Cache-Control header.

✅

This resource has a cache control header.

Cache-Control: no-cache, no-store, max-age=0, must-revalidate
❌

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-cache, no-store, max-age=0, must-revalidate
expires: Mon, 01 Jan 1990 00:00:00 GMT
🧭

Cache-Control

Cache-Control: no-cache, no-store, max-age=0, must-revalidate
  • ⏳
    Max Age
    (RFC)

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

    For example, since this response was fetched on May 17, 2024, 8:26:29 AM, it will become stale on May 17, 2024, 8:26:29 AM.

  • ♻️
    No Cache
    (RFC)
    The no-cache directive indicates that this response may be cached, but any cached response must be validated with the origin server before it can be used.
  • 🚫
    No Store
    (RFC)
    The no-store directive indicates that this response must not be stored in any cache.
  • ❗
    Must Revalidate
    (RFC)
    The must-revalidate directive indicates that when the response becomes stale, the cache must revalidate the cached response before it can be used again.
🗑️

Expires

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

Expires: Mon, 01 Jan 1990 00:00:00 GMT

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