Delivery
Cache
Understand how responses are cached, inspect variations, and purge content when it changes.
How caching works
GET and HEAD responses under 1 MB are cached, with TTL clamped from the origin's max-age header.
- Public, cacheable GET/HEAD responses
- TTL clamped from origin headers
- Hit ratio tracked on the overview
Cache variations
Serve different cached responses for the same URL based on request conditions.
- Vary by cookie, country, or header
- Cache rules scoped per domain
- Cache records mirrored in the dashboard
Purge content
Clear cached content immediately after a deploy or content change.
- Purge from the dashboard
- Purge by domain or key
- Stats reflect purge activity