Opened 12 years ago

Closed 8 years ago

#117 closed design (invalid)

cache invalidation upon update

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

Description

This text currently is only specified for HEAD and not GET:

If the new field values indicate that the cached entity differs from the current entity (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.

It's an equally good rule for GET as for HEAD, and having them aligned would help getting rid of cornercases such as the #23 question.

Change History (10)

comment:1 Changed 11 years ago by mnot@…

  • Component changed from non-specific to p2-semantics

comment:2 Changed 11 years ago by fielding@…

A 200 response to GET is already going to replace the cache entry, since the reason the client is receiving a 200 response is because the cached one is considered invalid.

comment:3 Changed 11 years ago by mnot@…

  • Milestone changed from unassigned to 06

Text should be moved to p6.

comment:4 Changed 11 years ago by julian.reschke@…

  • Milestone changed from 06 to unassigned

comment:5 Changed 10 years ago by mnot@…

  • Component changed from p2-semantics to p6-cache
  • Priority set to normal

comment:6 Changed 9 years ago by mnot@…

Another aspect - given a 200 response to a conditional request, is there a requirement that it MUST/SHOULD invalidate any existing cached entry?

comment:7 Changed 9 years ago by fielding@…

Have you considered the effect on read-only cache media? E.g., firmware and cd-roms can be used as an offline cache and it seems fairly critical that they not be invalidated unless absolutely necessary for interoperability.

comment:8 Changed 9 years ago by mnot@…

  • Owner set to mnot@…

comment:9 Changed 9 years ago by mnot@…

Prague editors: point out that only latest response is to be used

comment:10 Changed 8 years ago by mnot@…

  • Resolution set to invalid
  • Status changed from new to closed

No response from Henric; closing as WONTFIX.

Note: See TracTickets for help on using tickets.