W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2008

Re: server applying PUT to a resource other than the request-URI

From: Helge Hess <helge.hess@opengroupware.org>
Date: Tue, 21 Oct 2008 10:35:31 +0200
Message-Id: <4944B0C1-47F2-400C-AF75-315B81689A5A@opengroupware.org>
To: HTTP Working Group <ietf-http-wg@w3.org>

On 21.10.2008, at 09:46, Yves wrote:
> When you know that /new.txt will generate new URIs, the correct  
> method to trigger is is POST and clearly not PUT.

You don't know that the specific new.txt will generate new URIs, it  
was just an example. Of course you need to do the same If-None-Match:  
* iterations as usual.
And yes, of course new.txt is a very bad choice, high potential for  
conflict. Most CalDAV/CardDAV client would start with the UID of the  
item and then proceed.

Again: why is POST a bad choice? Because a client using POST wouldn't  
be able to create items in a regular WebDAV server. The suggestion has  
very bad downgrade behaviour. IMHO it has very little chance for  
adoption.

But anyways, I don't think this thread will lead anywhere, as  
usual ..., I'll quit :-)

Well, actually it gave (me) one new insight, so it apparently _was_  
worth the annual PUT-redirect posting :-)
A 307+Location is apparently accepted by everyone (?) as a method for  
producing server generated URLs in a HTTP compliant way. (might be a  
little harder for the server and client, but its a starting point).

Thanks,
   Helge
-- 
Helge Hess
http://zideone.com/
Received on Tuesday, 21 October 2008 08:36:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:56 GMT