Opened 10 years ago

Closed 9 years ago

#402 closed design (fixed)

Comparison function for If-Match and If-None-Match

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


In the definitions of If-Match and If-None-Match, we don't specify whether the weak or strong comparison function is to be used when these validations actually occur, although we spend a lot of text on when to use weak vs. strong ETags themselves.

Now, you might say that an origin server can decide whether to use the weak or strong function, but an intermediary or client cache doesn't have license to do weak comparison, and could cause a lot of trouble if it did. AFAICT we don't specify this, but I think we should.

Change History (6)

comment:1 Changed 10 years ago by mnot@…

  • Milestone changed from unassigned to 22

Resolution: both should be explicitly using the weak comparison function.

comment:2 Changed 10 years ago by mnot@…

  • Owner draft-ietf-httpbis-p4-conditional@… deleted

comment:3 Changed 10 years ago by fielding@…

From [2131]:

clarify that If-Match and If-None-Match use the weak comparison function, since otherwise weak etags would never work; addresses #402

comment:4 Changed 10 years ago by fielding@…

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

comment:5 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:6 Changed 9 years ago by mnot@…

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