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: Brian Smith <brian@briansmith.org>
Date: Mon, 20 Oct 2008 15:40:25 -0500
To: <julian.reschke@gmx.de>, <henrik@henriknordstrom.net>
Cc: <ietf-http-wg@w3.org>
Message-ID: <00cb01c932f4$15adf1e0$4109d5a0$@org>

Julian Reschke wrote:
> Henrik Nordstrom wrote:
> > On mån, 2008-10-20 at 22:12 +0200, Julian Reschke wrote:
> >> Henrik Nordstrom wrote:
> >>> I'll second Brians response here.
> >> Which part?
> >
> > The whole message with 3 alternatives, all three of them.

> Proposal 1 IMHO breaks the PUT semantics (that's why I started this
> thread).

Proposal 1 was: "Simply do allow that use case. WebDAV clients already expect the server to create the resources at the URI they are given. This is a pretty fundamental part of WebDAV; an extension of WebDAV that didn't support it isn't an extension at all."

In other words, just let the client pick the URI like we always have in WebDAV, and don't attempt to support servers that do not want to let the client pick the URI. There is nothing that breaks PUT's semantics there.

> > However, creating a new method for this is defenitely not the right
> > thing. Better to extend PUT to allow this use case by conditionally
> > relaxing the target resource URI requirements, or use POST.
> 
> I still do not see how this functionality can be implemented without
> breaking the semantics of PUT.

The functionality doesn't need to be implemented in the first place, so it doesn't matter.

- Brian
Received on Monday, 20 October 2008 20:40:53 GMT

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