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: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Fri, 24 Oct 2008 23:48:59 +0200
To: Brian Smith <brian@briansmith.org>
Cc: ietf-http-wg@w3.org
Message-Id: <1224884939.3231.184.camel@henriknordstrom.net>
On fre, 2008-10-24 at 16:24 -0500, Brian Smith wrote:
> Henrik Nordstrom wrote:
> > 2. If you absolutely must operate in this manner use POST for creating
> > the resource. There is no standard POST application protocol for
> > creating server named resources so invent your own ontop of POST. This
> > could be as simple as having the complete payload just as PUT, or a
> > more elaborate protocol with added meta data such as the forms POST
> > protocol or something similar, it's up to the application.
> 
> But, this doesn't work for WebDAV and extensions of it. For WebDAV you
> *must* let the client choose the name. Otherwise, your server isn't a WebDAV
> server.

I didn't say anything else. Looking at the problem scope from a general
HTTP point of view, not specific WebDAV.

I don't see why WebDAV servers can't also implement a POST interface for
creating resoures. Would be very odd if WebDAV prohibits this when it is
allowed by HTTP. But it's not part of the WebDAV application of HTTP.
But I would be very annoyed if installing WebDAV support made my photo
album application no longer can accept form based uploads of images
where the server names the image based on exif information in the image.

Regards
Henrik

Received on Friday, 24 October 2008 21:49:44 GMT

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