Opened 8 years ago

Closed 6 years ago

#227 closed design (fixed)

Combining HEAD responses

Reported by: mnot@… Owned by: mnot@…
Priority: normal Milestone: 19
Component: p6-cache Severity: Active WG Document
Keywords: Cc:

Description (last modified by mnot@…)

p2 defines how HEAD responses affect caches:

The response to a HEAD request is cacheable and &MAY; be used to satisfy a subsequent HEAD request; see &caching;. It also &MAY; be used to update a previously cached representation from that resource; if the new field values indicate that the cached representation differs from the current representation (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the cache &MUST; treat the cache entry as stale.

  1. This (i.e., the mechanics of how caches should combine responses) should be moved to p6
  2. If possible, it should be part of the existing section on combining responses
  3. It doesn't define how to combine other headers (p6 combining responses does; same algorithm?)
  4. p6 combining responses doesn't talk about what to do to the cache state if the ETag, etc. differ (this does); should we incorporate this there? See also #117, somewhat related.

Change History (10)

comment:1 Changed 8 years ago by mnot@…

  • Description modified (diff)

comment:2 Changed 8 years ago by mnot@…

  • Type changed from design to editorial

Looking into this, it's not valid to combine these.

  • HEAD doesn't update a stored response, it replaces it (because it needs to contain all headers, not just some like 304).
  • 304/204 handling of differing metadata is also likely to not be the same.

As such, only #1 really makes sense. Flipping to Editorial as a result.

comment:3 Changed 8 years ago by mnot@…

  • Component changed from non-specific to p6-cache

comment:4 Changed 8 years ago by mnot@…

  • Owner set to mnot@…

comment:5 Changed 7 years ago by mnot@…

  • Type changed from editorial to design

Flipping back to Design; there are deeper issues lurking here.

comment:6 Changed 7 years ago by mnot@…

From [1554]:

Move cache-specific HEAD language to p6; fully specify effects on cache. Addresses #227.

comment:7 Changed 7 years ago by mnot@…

  • Milestone changed from unassigned to 19
  • Resolution set to incorporated
  • Status changed from new to closed

comment:8 Changed 7 years ago by julian.reschke@…

From [1560]:

Note changes for [1554] (see #227)

comment:9 Changed 6 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:10 Changed 6 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.