Opened 11 years ago

Closed 10 years ago

#116 closed design (fixed)

Weak ETags on non-GET requests

Reported by: mnot@… Owned by: julian.reschke@…
Priority: urgent Milestone: 08
Component: p4-conditional Severity: Active WG Document
Keywords: Cc:

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

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

Download all attachments as: .zip

Change History (5)

Changed 11 years ago by julian.reschke@…

Proposed patch to part 4.

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

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

Fixed in [245]:

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

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

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

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

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

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

comment:4 Changed 10 years ago by julian.reschke@…

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

Fixed in [656]:

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

Note: See TracTickets for help on using tickets.