Response Cacheability

How does it work?

This criterion lets you match based on the instructions in the response's metadata and the Edge-Control header that determine whether the content is cacheable.

The response is considered uncachable when at least one of the following is true:

  • the no-store or bypass-cache directive is present in the metadata in the response header fields,
  • the Edge-Control header is present in the origin response.

Otherwise, the response is considered cacheable.

πŸ“˜

cache-control headers from the origin have no effect on Response Cacheability.

Operators

You can select the following logical conditions:

Value The Rule is True when...
isthe response header instructions include the specified cacheability status.
is notthe response header instructions do not include the specified cacheability status.

Fields

From the drop-down list, select the response cacheability status. Specify if the content cache is enabled (CACHEABLE), disabled (NO_STORE), or ignored (BYPASS_CACHE).


Did this page help you?