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

Ticket #293 (closed design: fixed)

Opened 3 years ago

Last modified 2 years ago

Interaction of request and response Cache-Control

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: 18
Component: p6-cache Severity: Active WG Document
Keywords: Cc:
Origin:

Description (last modified by julian.reschke@gmx.de) (diff)

The specification does not say how request Cache-Control affects the freshness algorithm, nor does it say how request CC extensions can or cannot affect response CC directives.

Change History

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

Partial proposal:

In 2.2, replace this:

the presented request and stored response are free from directives that would prevent its use (see Section 3.2 and Section 3.4), and

with this:

the presented request does not contain the 'no-cache' pragma (section 3.4), nor the 'no-cache' cache directive (section 3.2.1), unless the stored response is successfully validated (section 2.4).

the stored response does not contain the 'no-cache' cache directive (section 3.2.2), unless it is successfully validated (2.4).

Still to deal with: request max-age / max-stale / min-fresh

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

  • Description modified (diff)

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

max-stale is already taken care of in 2.3.3:

A cache MUST NOT return stale responses unless it is disconnected (i.e., it cannot contact the origin server or otherwise find a forward path) or doing so is explicitly allowed (e.g., by the max- stale request directive; see Section 3.2.1).

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

Proposal for max-age and min-fresh --

In 2.3 Freshness Model, change

Additionally, clients might need to influence freshness calculation. They can do this using several request cache directives, with the effect of either increasing or loosening constraints on freshness. See Section 3.2.1.

to

Additionally, clients can request modifications to freshness calculation -- either constraining or relaxing it -- by using the max-age and min-fresh request cache directives. See Section 3.2.1 for details.

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

  • Milestone changed from unassigned to 18

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

  • Owner draft-ietf-httpbis-p6-cache@tools.ietf.org deleted

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

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

Fixed in [1483]:

Clarify effects of request Cache-Control; closes #293.

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

  • Status changed from closed to reopened
  • Resolution fixed deleted

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

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

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

  • Status changed from closed to reopened
  • Resolution incorporated deleted

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

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