- From: Julian Reschke <julian.reschke@gmx.de>
- Date: 2012年7月10日 17:00:19 +0200
- To: Robert Brewer <fumanchu@aminus.org>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <4FFC4383.9020501@gmx.de>
On 2012年07月10日 16:55, Robert Brewer wrote: > Section 5.1 of draft-19 part 2 says, "An HTTP request representation, > when present, is always associated with an anonymous (i.e., > unidentified) resource." [1] That makes perfect sense for POST, but for > PUT it makes sense IMO to declare that the representation is associated > with the target resource. Or is the intent that the representation "is > *to become* associated", and is therefore considered anonymous before > the request had been handled? Yes, that's (IMHO) the intent. The decision is up to the server (after all, it could reject the request). > This is important for at least one reason: I believe this section in the > HTTP spec could be useful to establish a base URI for request entities > according to section 5.1 of the URI spec [2] (which itself might be > underspecified in this regard; it doesn't say much about operations > other than retrieval). Do you need that functionality until the time the PUT has succeeded? > ... Best regards, Julian
Received on Tuesday, 10 July 2012 15:01:25 UTC