- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: Tue, 5 Nov 2019 07:48:03 +0200 (EET)
- To: Mark Nottingham <mnot@mnot.net>
- CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP Working Group <ietf-http-wg@w3.org>
https://tools.ietf.org/html/draft-ietf-httpbis-cache-header-02#section-2
| Each member of the parameterised list represents a cache that has
| handled the request. The first member of the list represents the
| cache closest to the origin server, and the last member of the list
| represents the cache closest to the user agent (possibly including
| the user agent's cache itself, if it chooses to append a value).
but
https://tools.ietf.org/html/draft-ietf-httpbis-cache-header-02#section-3
| Going through two layers of caching, both of which were hits, and the
| second collapsed with other requests:
|
| Cache-Status: "CDN Company Here"; res-fresh=545,
| OriginCache; cache-fresh=1100; collapse-hit=?1
So "CDN Company Here" is the cache closest to the origin server ?
However name indicates that OriginCache is the cache closest to
the origin server, but specification says that first member
("CDN Company Here") is the cache closest to the origin server.
/ Kari Hurtta
Received on Tuesday, 5 November 2019 05:48:15 UTC