← All tools
OMNIKITZ GUIDES

HTTP Cache Debugger: practical guide

By Team Hypomnema · Web & network

Explain freshness, validators and browser versus shared-cache behavior.

Use the guide alongside the working tool.

Open HTTP Cache Debugger →

Explicit sample

HTTP/1.1 200 OK
Date: Wed, 28 Oct 2026 09:00:00 GMT
Cache-Control: public, max-age=3600, s-maxage=600, stale-while-revalidate=60
Age: 120
ETag: "asset-v3"
Vary: Accept-Encoding

Explain freshness, validators and browser versus shared-cache behavior.

Prepare your input

Explain freshness, validators and browser versus shared-cache behavior.

Use the labeled working sample to see the accepted format. Replace it with your own input, select the relevant options, and run the tool. Supporting controls remain in the bounded editor window.

Understand the result

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.

Export deliberately

Record exports contain the complete selected dataset; reports summarize up to 100 records. Artifacts contain the actual generated configuration, sanitized capture or compressed bytes. Review configuration before publishing it.

Input stays in browser memory. No remote page fetching, account access or file upload is performed.

Ready to apply this workflow?

Try HTTP Cache Debugger →

Explore a related workflow

All practical guides →

Keep your original files and review the result. Found unclear instructions? Contact Team Hypomnema.

YOUR BROWSER, YOUR CHOICE