Opened 9 years ago

Closed 9 years ago

#21 closed design (fixed)

PUT side effects

Reported by: mnot@… Owned by:
Priority: Milestone: 02
Component: p2-semantics Severity:
Keywords: Cc:

Description

2616 specifically allows PUT to have side effects;

A single resource MAY be identified by many different URIs. For example, an article might have a URI for identifying "the current version" which is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in several other URIs being defined by the origin server.

HTTP/1.1 does not define how a PUT method affects the state of an origin server.

and it also says (in the context of PUT)

If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response.

So, if I PUT something to /foo, and it has the side effect if creating /foo;2006-04-03, is the response required to be a 201 Created?

I.e., read literally, the above requirement requires a 201 Created when PUT results in *any* resource being created -- even as a side effect.

This is IMO unnecessarily constraining, and should be relaxed; e.g., changed to something like

Change History (4)

comment:1 Changed 9 years ago by mnot@…

Proposal:

"If a new resource is created at the Request-URI, the origin server MUST inform the user agent via the 201 (Created) response."

comment:2 Changed 9 years ago by mnot@…

  • Component set to semantics
  • Milestone set to unassigned
  • version set to d00

comment:3 Changed 9 years ago by mnot@…

  • Milestone changed from unassigned to 02

Proposal accepted.

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

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

Fixed in [180]:

Resolve #21: clarify that 201 is only required when a new resource is being created at the Request-URI (closes #21)

Note: See TracTickets for help on using tickets.