Ticket #403 (closed design: fixed)
Authentication and caching - max-age
|Reported by:||email@example.com||Owned by:||firstname.lastname@example.org|
|Component:||p7-auth||Severity:||In WG Last Call|
While reviewing the clauses for cacheability I find an undefined case which can reasonably be expected to appear in real-world traffic.
Comparing p6 section 220.127.116.11 and 18.104.22.168 it is clear that response Cache-Control "no-cache" with no values is semantically equivalent to "must-revalidate, max-age=0".
p7 section 4.1 clause 2 states that responses with "must-revalidate" MAY be cached for use on later requests provided revalidation is done.
Assuming that p7 clause is true, I see no reason why "no-cache" response control cannot be also added to p7 section 4.1 list of exceptions along with must-revalidate.
- Status changed from new to closed
- Resolution set to incorporated
- Status changed from closed to reopened
- Resolution incorporated deleted