Opened 7 years ago

Closed 7 years ago

#363 closed design (fixed)

Rare cases

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

Description

p4 2.4 Rules for When to Use Entity-tags and Last-Modified Dates notes at the end:

HTTP/1.0 clients and caches might ignore entity-tags. Generally, last-modified values received or used by these systems will support transparent and efficient caching, and so HTTP/1.1 origin servers still ought to provide Last-Modified values. In those rare cases where the use of a Last-Modified value as a validator by an HTTP/1.0 system could result in a serious problem, then HTTP/1.1 origin servers should not provide one.

What are these "rare cases", and how is a server to know when it's encountering one?

Change History (5)

comment:1 Changed 7 years ago by mnot@…

  • Milestone changed from unassigned to 20

Proposal: remove the last sentence.

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

From [1703]:

Remove mention of "rare cases" with respect to HTTP/1.0 (see #363)

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

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

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.