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 stage is processed |
|---|---|
| content-policy | As the request is received (for only some requests - typically when security products or cloudlets are in use). |
| client-request | When the request is received. This is the primary stage for most processing. |
| client-request-body | After the client-request stage, if the request has a body (e.g. for POST requests). |
| ipa-response | After the response is received from the Intermediate Processing Agent (IPA) server. |
| cache-hit | After the object is loaded from cache and verified. |
| forward-start | Immediately before the Akamai server selects a forward server to connect to (either a customer origin or a cache-h parent). |
| forward-request | Immediately before the server tries to connect to a forward server (either a customer origin or a cache-h parent), or immediately after it has decided to reuse a persistent connection (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 have been successfully parsed. |
| forward-insufficient-response | After the object is received from a customer origin, and only when forward TLS handshake fails. This stage runs instead of the forward-response stage. |
| client-response | Immediately before the response is returned to the client. |
| client-done | Immediately after serving the response to the client. This stage is used only for logging functionality, as no further changes can be made to the response. |
Updated 14 days ago