Ticket #117 (closed design: invalid)
cache invalidation upon update
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||p6-cache||Severity:||Active WG Document|
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.
- Priority set to normal
- Component changed from p2-semantics to p6-cache