Opened 14 years ago
Closed 13 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)
Change History (5)
Changed 14 years ago by julian.reschke@…
comment:1 Changed 14 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 13 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 13 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 13 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Proposed patch to part 4.