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

Ticket #363 (closed design: fixed)

Opened 2 years ago

Last modified 22 months ago

Rare cases

Reported by: mnot@pobox.com Owned by: draft-ietf-httpbis-p4-conditional@tools.ietf.org
Priority: normal Milestone: 20
Component: p4-conditional Severity: In WG Last Call
Keywords: Cc:
Origin: http://www.w3.org/mid/D1DACF74-AE6D-4172-81CD-0F878DA37B90@mnot.net

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

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

  • Milestone changed from unassigned to 20

Proposal: remove the last sentence.

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

From [1703]:

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

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

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

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

  • Status changed from closed to reopened
  • Resolution incorporated deleted

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

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