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

Ticket #353 (closed design: fixed)

Opened 2 years ago

Last modified 23 months ago

Multiple values in Cache-Control header fields

Reported by: mnot@pobox.com Owned by: draft-ietf-httpbis-p6-cache@tools.ietf.org
Priority: normal Milestone: 20
Component: p6-cache Severity: In WG Last Call
Keywords: Cc:
Origin: http://www.w3.org/mid/18AB958B-CC87-44B4-9C3A-D0416C318834@niven-jenkins.co.uk

Description

In the HTTPBIS documents there are now specific directions for dealing with multiple values within Host or Content-Length headers.

However, there doesn't appear to be a general conflict resolution strategy.

For example, if there are multiple Expires headers, valid or invalid (but assuming at least one valid one), matching or different, which takes precedence? Or must the set be treated invalid? Always?

If "Cache-Control: max-age=5, max-age=10" is received, what is the expected behaviour?

Similar concerns apply to other sections: what do multiple ETag or Last-Modified headers mean? Or multiple Content-Range headers (the same as multiple Content-Length headers one would assume).

Attachments

353.diff (1.1 KB) - added by julian.reschke@gmx.de 2 years ago.
Proposed patch for Part 6

Change History

Changed 2 years ago by julian.reschke@gmx.de

Proposed patch for Part 6

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

From [1731]:

add advice on how to treat multiple instances of freshness information (see #353)

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

  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 20

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

  • Summary changed from Multiple values in Cache-Control headers to Multiple values in Cache-Control header fields

comment:4 Changed 23 months ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

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

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