Metadata Stage

How does it work?

Matches how the current rule corresponds to low-level syntax elements in translated XML metadata, indicating progressive stages as each edge server handles the request and response.


To use this match, you need to be thoroughly familiar with how ​Akamai​ edge servers process requests. Contact your ​Akamai​ technical representative if you need help, and test thoroughly on staging before activating on production.


OptionWhen the rule responds
content-policyAs the request is received.
client-requestAs the request is received, or immediately following content-policy stage, if the content-policy stage is run.
client-request-bodyAfter the request has been received.
ipa-responseAfter the response is received from the intermediate processing agent server.
cache-hitAfter the object is loaded from cache and is sanity checked.
forward-startImmediately before the Akamai server selects a forward server to connect to.
forward-requestImmediately before the server tries to connect to a forward server, or right after it has decided to reuse a PConn.
forward-responseAfter the object is received from a forward server (either a customer origin or a cache-h parent), and the response headers are successfully parsed.
forward-insufficient-responseAfter the object is received from the origin server, and only when forward TLS handshake fails, instead of the forward-response stage.
client-responseBefore we construct the reply for the client.
client-doneImmediately after serving the client.