ReadonlyrequestedThe time the request was sent, as milliseconds since the epoch.
Taken as the instant a stored response starts ageing, so that its age accounts for the time it spent in transit.
ReadonlyreceivedThe time the response was received, as milliseconds since the epoch.
Taken as the instant the freshness of a stored response is measured from where the origin server states no generation time of its own, rather than the moment the response was handed to a store.
ReadonlystatusThe status code of the stored response.
ReadonlyheadersThe header fields of the stored response, keyed by lowercase field name.
A field the response doesn't state is reported as undefined, so that a name is read without first checking
that it is stated.
The age field reports what the exchange that last delivered or confirmed the content stated, so that an entry
refreshed by a revalidation ages from that exchange rather than from the original delivery.
ReadonlybodyThe content of the stored response.
Optional ReadonlyvariantsThe cache keys the variants of the stored response are held under.
Stated on the entry a resource is looked up through, where the origin server answers it with varying responses, so that giving up the resource gives up every variant held for it. A store is to report it as it was stored, like every other field of an entry.
Cached response.
Carries all the state required to serve a response again. An entry is self-contained and replayable, so a Store hands out the same one as many times as it is asked for, and is free to serialise it and keep it beyond the life of the process.