Ticket #225 (closed design: fixed)
PUT side effect: invalidation or just stale?
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||non-specific||Severity:||Active WG Document|
p2 7.6 (PUT):
If the request passes through a cache and the Effective Request URI identifies one or more currently cached entities, those entries SHOULD be treated as stale.
p6 2.5 (Request Methods that Invalidate):
Here, "invalidate" means that the cache will either remove all stored responses related to the Effective Request URI, or will mark these as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent request.
These sections conflict regarding the side effects of PUT; p2 only wants it marked stale, whereas p6 says it cannot be served stale, but must (at least) be revalidated.
comment:10 Changed 3 years ago by firstname.lastname@example.org
- Status changed from new to closed
- Resolution set to incorporated
comment:11 Changed 3 years ago by email@example.com
- Status changed from closed to reopened
- Resolution incorporated deleted