HTTP Cache-Status

Last Updated
Available Formats



Plain text

Registry included below

HTTP Cache-Status

Registration Procedure(s)
Expert Review
Available Formats

Name Description Reference
hit The request was satisfied by the cache; i.e., it was not forwarded, and the response was obtained from the cache. [RFC-ietf-httpbis-cache-header-10]
fwd The request went forward towards the origin, and why. [RFC-ietf-httpbis-cache-header-10]
fwd-status The status code (see [draft-ietf-httpbis-semantics-17], Section 15) the next hop server returned in response to the forwarded request. [RFC-ietf-httpbis-cache-header-10]
ttl The response's remaining freshness lifetime (see [draft-ietf-httpbis-cache-17], Section 4.2.1) as calculated by the cache, as an integer number of seconds, measured as closely as possible to when the response header section is sent by the cache. [RFC-ietf-httpbis-cache-header-10]
stored The cache stored the response (see [draft-ietf-httpbis-cache-17], Section 3); a true value indicates that it did. [RFC-ietf-httpbis-cache-header-10]
collapsed This request was collapsed together with one or more other forward requests (see [draft-ietf-httpbis-cache-17], Section 4); if true, the response was successfully reused; if not, a new request had to be made. [RFC-ietf-httpbis-cache-header-10]
key Conveys a representation of the cache key (see [draft-ietf-httpbis-cache-17], Section 2) used for the response. [RFC-ietf-httpbis-cache-header-10]
detail Allows implementations to convey additional information not captured in other parameters; for example, implementation-specific states, or other caching-related metrics. [RFC-ietf-httpbis-cache-header-10]