Opened 13 years ago
Closed 11 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.
- This (i.e., the mechanics of how caches should combine responses) should be moved to p6
- If possible, it should be part of the existing section on combining responses
- It doesn't define how to combine other headers (p6 combining responses does; same algorithm?)
- 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 13 years ago by mnot@…
- Description modified (diff)
comment:2 Changed 13 years ago by mnot@…
- Type changed from design to editorial
comment:3 Changed 13 years ago by mnot@…
- Component changed from non-specific to p6-cache
comment:4 Changed 12 years ago by mnot@…
- Owner set to mnot@…
comment:5 Changed 11 years ago by mnot@…
- Type changed from editorial to design
Flipping back to Design; there are deeper issues lurking here.
comment:6 Changed 11 years ago by mnot@…
comment:7 Changed 11 years ago by mnot@…
- Milestone changed from unassigned to 19
- Resolution set to incorporated
- Status changed from new to closed
comment:8 Changed 11 years ago by julian.reschke@…
comment:9 Changed 11 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:10 Changed 11 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
Looking into this, it's not valid to combine these.
As such, only #1 really makes sense. Flipping to Editorial as a result.