* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #403 (closed design: fixed)

Opened 2 years ago

Last modified 18 months ago

Authentication and caching - max-age

Reported by: mnot@pobox.com Owned by: draft-ietf-httpbis-p7-auth@tools.ietf.org
Priority: normal Milestone: 22
Component: p7-auth Severity: In WG Last Call
Keywords: Cc:
Origin: http://www.w3.org/mid/507A332B.3020301@treenet.co.nz

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

comment:1 Changed 2 years ago by mnot@pobox.com

From [1999]:

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

comment:2 Changed 2 years ago by mnot@pobox.com

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

comment:3 Changed 2 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 22

comment:4 Changed 2 years ago by julian.reschke@gmx.de

From [2000]:

note change for [1999] (see #403)

comment:5 Changed 18 months ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:6 Changed 18 months ago by mnot@pobox.com

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