Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#267 closed design (fixed)

clarify PUT semantics

Reported by: julian.reschke@… Owned by:
Priority: normal Milestone: 13
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:

Description (last modified by julian.reschke@…)

There's a permathread about PUT-for-partial-update.

We should clarify that PUT can be more than "store this payload verbatim", but that the final state should not depend on the previous state of the resource (except when by design; such when doing versioning...)

Change History (5)

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

I believe this can be closed as fixed as per [1158].

comment:2 Changed 12 years ago by fielding@…

  • Milestone changed from unassigned to 13
  • Resolution set to incorporated
  • Status changed from new to closed

Yes, fixed in [1158]. The relevant paragraph added is

An origin server SHOULD reject any PUT request that contains a Content-Range header field, since it might be misinterpreted as partial content (or might be partial content that is being mistakenly PUT as a full representation). Partial content updates are possible by targeting a separately identified resource with state that overlaps a portion of the larger resource, or by using a different method that has been specifically defined for partial updates (for example, the PATCH method defined in [RFC5789]).

comment:3 Changed 12 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:4 Changed 12 years ago by mnot@…

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

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

  • Description modified (diff)
Note: See TracTickets for help on using tickets.