HTTP Cache Debugger
Explain freshness, validators and browser versus shared-cache behavior.
Private by design
Your inputs stay on your device and are not sent to our servers. Optional usage analytics does not receive your files or tool inputs.
How to use HTTP Cache Debugger
- Add your source or choose Try sample; Undo sample restores previous inputs.
- Choose the workflow and review results, diagnostics and method notes.
- Download the useful artifact, complete records or a summary report.
What are the limits of HTTP Cache Debugger?
Evaluates supplied response/request headers and status, using RFC-style explicit freshness from s-maxage/max-age/Expires and Age plus Date. No heuristic freshness or live fetch. no-cache allows storage but requires validation; no-store blocks storage. Vary:* cannot be reused. Request directives and authorization affect the chosen cache; malformed or conflicting directives are reported. Text input: 5 MB total. XML external entities and includes are disabled. No automatic local storage. Reports summarize the selected result; CSV/JSON retain complete records.