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

Ticket #116 (closed design: fixed)

Opened 6 years ago

Last modified 5 years ago

Weak ETags on non-GET requests

Reported by: mnot@pobox.com Owned by: julian.reschke@gmx.de
Priority: urgent Milestone: 08
Component: p4-conditional Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/A18E9C08893FC84CB79657C5B27705EE1E279B3AFD@NA-EXMSG-C107.redmond.corp.microsoft.com

Description

RFC2616 limits the use of weak ETags to full (non-subrange) GET requests.

While the limitation on ranged requests makes sense, weak ETag validation is useful on full non-GET requests; e.g., PUT with If-Match.

Attachments

i116.diff (2.1 KB) - added by julian.reschke@gmx.de 6 years ago.
Proposed patch to part 4.

Change History

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

Proposed patch to part 4.

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

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

Fixed in [245]:

Resolve #116: allow weak entity tags in all requests except range requests (closes #116).

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

  • Priority set to normal
  • Status changed from closed to reopened
  • Resolution fixed deleted

Section about If-Match needs to be updated as well.

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

  • Owner set to julian.reschke@gmx.de
  • Priority changed from normal to urgent
  • Status changed from reopened to new
  • Milestone changed from unassigned to 08

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

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

Fixed in [656]:

Resolve #116: If-Match was still requiring strong matches (closes #116)

Note: See TracTickets for help on using tickets.