Opened 15 years ago

Closed 15 years ago

Last modified 12 years ago

#112 closed editorial (fixed)

PUT - "store under" vs "store at"

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


8.6.  PUT
    The PUT method requests that the enclosed entity be stored under the
    supplied Request-URI.

Several people thought "under" implies "at a subpath of the Request-URI". To reduce confusion, this should be changed from "under" to "at".

Change History (3)

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

  • Owner set to julian.reschke@…

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

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

Fixed in [241]:

Resolve #112: replace "to be stored under the supplied Request-URI" by "... at ....". (closes #112).

comment:3 Changed 12 years ago by fielding@…

From [1158]:

Replaced the general prohibition on unrecognized Content-* header fields with a specific prohibition of Content-Range (the only field for which it is an actual problem) and a general requirement regarding checking for consistency. Unfortunately, this required rewriting the entire section on PUT to get rid of the misconceptions about storing resources and reflect how PUT is actually implemented in practice.

Addresses #79, #102, #103, #104, #112, #180, #231, and #267

Note: See TracTickets for help on using tickets.