FreshTraceHTTP CACHE POLICY LAB
Cache headers.
Clear answers.
Stop guessing what gets served. Paste headers, move through time,
and see the browser and CDN make their decisions.
↗One response.
Two caches.
Every decision explained.
Two caches.
Every decision explained.
TIME TRAVEL
When does the next request arrive?
75seconds after receipt
FreshBackground validationOn origin errorContact origin
What changes at this moment?
Follow the decision
Take the explanation with you.A reproducible scenario or a ready-to-share report.
A standards-based model of a complete GET 200 response. Matching URL and cache key assumed. Without capture times: zero transit, receipt at Date. No heuristic TTL or provider overrides.