Return Cache Status

This behavior generates a response header with information about cache status.

How it works

This behavior can provide information whether the response came from the ​Akamai cache, or from the origin. Status values report with either of these forms of syntax, depending on whether you’re deploying traffic using SureRoute or Tiered Distribution:

{status} from child
{status} from child, {status} from parent

The status value can be any of the following:

  • Hit: The object was retrieved from ​Akamai’s cache.
  • Miss: The object wasn’t found in the ​Akamai​ cache.
  • RefreshHit: The object was found in ​Akamai’s cache, but was stale, so an If-Modified-Since request was made to the customer origin, with 304 as the response code, indicating unmodified content.
  • HitStale: The object was found in ​Akamai’s cache and was stale, but a more recent object wasn’t available from the customer’s origin, so the cache served the stale object to the client.
  • Constructed: The Construct response behavior directly specified the response to the client.
  • Redirect: The ​Akamai​ edge configuration specified a redirect, typically by executing the Redirect, Redirect Plus or Edge Redirector Cloudlet behaviors.
  • Error: An error occurred, typically when authorization is denied or the request is rejected by the Web Application Firewall (WAF).

Features and options

Field What it does
Response Header name Specifies the name of the HTTP header in which to report the cache status value.


Was this article helpful?

Related Articles