Caching
Cache policies control whether HTTP responses are eligible for caching and how cached responses are used. A cache hit can serve a response without contacting your origin.
Route controls
| Field | Choices or purpose |
|---|---|
doCaching | Enables or overrides caching for the selected route |
cachePolicyId | Selects a managed cache policy |
cacheQueryStringMode | standard, ignoreQueryString or noQueryString |
cacheStatusHeaderEnabled | Controls cache status response headers |
cacheEdgeLocationHeaderEnabled | Controls cache location response headers |
Purge and activation
A managed purge advances a scoped checkpoint. Once that checkpoint reaches the request path, later requests use the changed cache namespace. Purge does not establish that every previously stored byte has been physically removed.
Cache policy validation and publication take place after the desired state changes. API success alone does not establish cache behavior at every serving location. Compare saved policy settings with repeated requests to a known cacheable resource and its origin behavior.
TODO(verify): Confirm a complete customer cache verification example with exact response header names and values.