Opened 7 years ago

Closed 6 years ago

#403 closed design (fixed)

Authentication and caching - max-age

Reported by: mnot@… Owned by: draft-ietf-httpbis-p7-auth@…
Priority: normal Milestone: 22
Component: p7-auth Severity: In WG Last Call
Keywords: Cc:

Description

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 7.2.2.3 and 7.2.2.5 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.

Change History (6)

comment:1 Changed 7 years ago by mnot@…

From [1999]:

Replace caching details with reference to p6; addresses #403.

comment:2 Changed 7 years ago by mnot@…

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

comment:3 Changed 7 years ago by mnot@…

  • Milestone changed from unassigned to 22

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

From [2000]:

note change for [1999] (see #403)

comment:5 Changed 6 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:6 Changed 6 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.