Applies to: Protocol and format interpretation for developers inspecting authorized media delivery.
The useful distinctions
- Age is expressed as a non-negative number of seconds.
- It communicates an estimate of response age.
- A received Age value is not a media playback duration.
Start from the age already present
A response can arrive with some of its freshness lifetime already consumed. In the simplified example, a 60-second lifetime and an observed age of 18 leave 42 seconds before the declared freshness boundary. Starting a fresh 60-second timer at receipt would silently add time that the policy did not grant. Label the 42-second result as a simplified estimate because the full cache age calculation also accounts for relevant timing observations.
Keep the calculation in its lane
An age reading is not a speed test, a count of frames waiting in a buffer, or the delay between an event and a television screen. It concerns the response's cache history. If the response is a manifest, referenced segments have their own response histories and policies. A useful diagnostic worksheet therefore records the manifest response and each investigated child resource independently. When the estimate reaches zero, report that the declared freshness allowance has been consumed; do not infer that the object becomes corrupt or disappears. Revalidation, replacement, and permitted stale handling are different follow-on decisions that require additional policy information. At a later observation with an estimated age of sixty-five seconds, the same simplified worksheet reports five seconds beyond freshness. A negative remainder is a boundary result, not permission to restart the timer.
Worked example · synthetic
Under the deliberately simplified timeline, 60 − 18 = 42 seconds remain. This arithmetic is an explanatory estimate, not an implementation of the complete HTTP cache age algorithm.
Synthetic text example; no network operation has been performed.
HTTP/MIME line endings are CRLF. Request URL context, where labelled, is commentary rather than a wire field. No message was transmitted.
HTTP/1.1 200 OK
Date: Sun, 08 Nov 2026 08:00:00 GMT
Cache-Control: max-age=60
Age: 18
Content-Length: 0
Check the interpretation
- Reject negative Age values.
- Do not reset the lifetime at receipt.
- State that transit and residence timing can refine the estimate.