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.
| Option | When the rule responds |
|---|---|
| content-policy | As the request is received. |
| client-request | As the request is received, or immediately following content-policy stage, if the content-policy stage is run. |
| client-request-body | After the request has been received. |
| ipa-response | After the response is received from the intermediate processing agent server. |
| cache-hit | After the object is loaded from cache and is sanity checked. |
| forward-start | Immediately before the Akamai server selects a forward server to connect to. |
| forward-request | Immediately before the server tries to connect to a forward server, or right after it has decided to reuse a PConn. |
| forward-response | After 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-response | After the object is received from the origin server, and only when forward TLS handshake fails, instead of the forward-response stage. |
| client-response | Before we construct the reply for the client. |
| client-done | Immediately after serving the client. |
Updated about 2 years ago