- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 6 Nov 2019 10:39:15 +1100
- To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Thanks, Kari. This is what I get for doing a draft revision right before the deadline...
Will fix for the next draft.
Cheers,
> On 5 Nov 2019, at 4:48 pm, Kari Hurtta <hurtta-ietf@elmme-mailer.org> wrote:
>
> 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
>
--
Mark Nottingham https://www.mnot.net/
Received on Tuesday, 5 November 2019 23:39:26 UTC