W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: PUT and DELETE methods in 200 code

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 04 Apr 2011 14:43:21 +0200
Message-ID: <4D99BCE9.8090101@gmx.de>
To: mike amundsen <mamund@yahoo.com>
CC: public-html@w3.org
On 04.04.2011 14:15, mike amundsen wrote:
> On Mon, Apr 4, 2011 at 03:36, Julian Reschke<julian.reschke@gmx.de>  wrote:
>> On 04.04.2011 07:05, mike amundsen wrote:
>>>
>>> Julian:
>>>
>>> Can you post one or more typical HTTP request/response examples of how
>>> PUT/DELETE interactions work for WebDAV servers today? This would help
>>> me better understand what is/is-not possible w/ HTML FORMS that
>>> support PUT/DELETE.
>>> ...
>>
>> WebDAV clients usually aren't interested in the response bodies for
>> successful PUT/DELETE requests; for them what matters is just the status
>> code.
> I assume this to mean that agents talking to these WebDAV servers
> usually just receive status codes in responses w/o bodies. IOW, 200
> w/o bodies as well as 201/202/204, right?

Right.

> Is 201 a common response to PUT for these servers? 202? 204? Is 204
> the most common response for DELETE? or 200?

PUT: 200 is common for update, 201 for create (as specified). I've never 
seen a 204 or a 202.

DELETE: 200 and 204 are common. Never seen 201 (that would be... 
surprising) or 202.

> ...

BR, Julian
Received on Monday, 4 April 2011 12:44:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:27 GMT