Opened 7 years ago

Closed 7 years ago

#353 closed design (fixed)

Multiple values in Cache-Control header fields

Reported by: mnot@… Owned by: draft-ietf-httpbis-p6-cache@…
Priority: normal Milestone: 20
Component: p6-cache Severity: In WG Last Call
Keywords: Cc:

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 (1)

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

Download all attachments as: .zip

Change History (6)

Changed 7 years ago by julian.reschke@…

Proposed patch for Part 6

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

From [1731]:

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

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

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

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

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

comment:4 Changed 7 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:5 Changed 7 years ago by mnot@…

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