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

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Mon, 20 Oct 2008 22:35:09 +0200
• To: Helge Hess <helge.hess@opengroupware.org>
• CC: HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <48FCEB7D.80407@gmx.de>

Helge Hess wrote:
> 
> Hm, I wonder whether we could just use a different header, NOT location. 
> Something like this:
> 
>   PUT /new.txt
>   Accept-Relocation: same-col, same-server, full
> 
>   HTTP/1.x 201 Created
>   Relocation: /123.txt
> 
> would that possibly work for everyone?

It's just a new request header that modifies the behavior of PUT to do 
something else-but-similar.

And, again, how does a client find out about the request-URI? You will need

   If-None-Match: *

to avoid unintentional overwrites on /new.txt, but as soon as you 
include it, a conforming server will have to reject the request with 412 
if /new.txt is already taken.

How exactly is that better than POST, which already can have that semantics?

BR, Julian

Received on Monday, 20 October 2008 20:35:54 UTC