HTTP Cache Freshness Simulator

Model cache age and freshness from supplied headers and explicit UTC timestamps.

On-device No sign-up Free to use

Calculate cache scenario controls

?

Processed in your browser. Your inputs stay on this device.

Showing an example. Change the fields, then use calculate cache scenario to update it.

Result

Showing an example.

Combine Age 20 with a two-second response delay and 58 seconds of resident time to obtain age 80 against max-age 120.

Current age: 80 seconds; freshness lifetime: 120 seconds.

Loading the tool. Your result will appear here.

https://usefreetools.net/http-cache-freshness-simulator · 20 November 2026

Was this helpful?

How to use HTTP Cache Freshness Simulator

  1. Paste observed response headers and enter request-sent, response-received and proposed reuse timestamps in UTC, ending in Z.
  2. To derive the latter times, enter elapsed seconds in the helper and select Apply elapsed times in UTC. Editing the helper alone does not change the original timestamps.
  3. Choose shared/private cache and supply the Authorization and Vary-match assumptions from your evidence.
  4. Read the updated age calculation alongside storage, validation and Vary observations. Export the scenario if needed; fresh age alone does not authorize reuse.

Example: HTTP Cache Freshness Simulator

Combine Age 20 with a two-second response delay and 58 seconds of resident time to obtain age 80 against max-age 120.

You add
Observed response headers: Date: Thu, 01 Oct 2026 10:00:00 GMT Age: 20 Cache-Control: public, max-age=120 ETag: "sample"; Request sent (UTC ISO time): 2026-10-01T10:00:00Z; Response received (UTC ISO time): 2026-10-01T10:00:02Z; Reuse time (UTC ISO time): 2026-10-01T10:01:00Z; Cache kind: shared; Request includes Authorization: false; Required Vary request fields match: unknown
You get
Current age: 80 seconds; freshness lifetime: 120 seconds.

Options

Cache kind
Shared caches use s-maxage when present; private caches use the applicable max-age or Expires evidence.
Vary matching
A fresh age does not establish request-field matching. Enter a match only when the required request evidence supports it.

Supported inputs and limits

  • A selected stored GET/200 response model with 20,000 header characters and bounded nonnegative integer age directives.
  • UTC times must be ordered.
  • No heuristic freshness when explicit evidence is missing.
  • Qualified directives and other HTTP cases need separate review; this is not a full cache implementation.
  • Request directives, validator success, partial responses and stale extensions are not simulated.
More details

No live cache/server is inspected or contacted.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Freshness and permission to reuse are separate

The age calculation accounts for response delay and time spent in the cache. no-store, private, authorization, Vary and no-cache can restrict storage or reuse even while an explicit lifetime remains. Missing Date or freshness evidence stays unknown instead of receiving a guessed heuristic lifetime.

Questions about HTTP Cache Freshness Simulator

Does a fresh result guarantee reuse?

No. Review the separate storage, validation and Vary observations.

What if Date is unavailable?

Exact current age remains unknown in this selected model.

Are stale responses always forbidden?

This report does not model every stale extension or request permission; it identifies the stated restrictions.

Page updated · Project managed by Tony Hines · Report a problem with HTTP Cache Freshness Simulator