Delivery
How caching works
The proxy caches eligible responses in fast memory storage and mirrors the record in the database, so cache state is fast to read at request time and still visible from the dashboard.
How it works
- Only public, cacheable GET/HEAD responses under 1 MB are eligible
- TTL comes from the origin's max-age header, clamped to platform limits rather than trusted outright
- Cache hit ratio is one of the headline metrics on the dashboard overview
Good to know
- A database record mirrors the cached payload for reporting and purge lookups, unique per tenant and cache key