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:
bypass-cachedirective is present in the metadata in the response header fields,
Edge-Controlheader is present in the origin response.
Otherwise, the response is considered cacheable.
cache-controlheaders from the origin have no effect on Response Cacheability.
You can select the following logical conditions:
|The Rule is True when...
|the response header instructions include the specified cacheability status.
|the response header instructions do not include the specified cacheability status.
From the drop-down list, select the response cacheability status. Specify if the content cache is enabled (
CACHEABLE), disabled (
NO_STORE), or ignored (
Updated over 1 year ago