- From: Mark Baker <distobj@acm.org>
- Date: Mon, 3 Apr 2006 20:01:39 -0500
- To: "Mark Nottingham" <mnot@yahoo-inc.com>
- Cc: ietf-http-wg@w3.org
On 4/3/06, Mark Nottingham <mnot@yahoo-inc.com> wrote: > > 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? Seems so. > 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 > > "If a new resource is created at the Request-URI, the origin server > MUST inform the user agent via the 201 (Created) response." Hmm, *that* seems more constraining to me; could the server not just return a Location header with value "/foo;2006-04-03" in the 201? Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
Received on Tuesday, 4 April 2006 01:01:46 UTC