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

Re: PUT and DELETE methods in 200 code

From: mike amundsen <mamund@yahoo.com>
Date: Mon, 4 Apr 2011 09:24:18 -0400
Message-ID: <BANLkTikUb7epxzpVKC+mxkqGfo-kvatBFQ@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: public-html@w3.org
All makes sense to me.

Are the following assumptions (for WebDAV servers) correct?
- 200 OK responses always include a body
- 201 CREATED responses always include a Location header
- 204 NO CONTENT respones carry no body and no Location header

MCA

On Mon, Apr 4, 2011 at 08:43, Julian Reschke <julian.reschke@gmx.de> wrote:
> 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.
Received on Monday, 4 April 2011 13:24:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:24 UTC