W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2006

Re: DELETE and ETag

From: Mark Baker <distobj@acm.org>
Date: Sun, 5 Nov 2006 12:56:09 -0500
Message-ID: <c70bc85d0611050956sd93d5dj616e7aa89db02bf6@mail.gmail.com>
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: "HTTP Working Group" <ietf-http-wg@w3.org>

It's also redefining the meaning of DELETE.

On 11/4/06, Julian Reschke <julian.reschke@gmx.de> wrote:
>
> Hi,
>
> I just noticed a funny requirement in Section 8.4 of
> draft-ietf-simple-xcap-12 (<draft-ietf-simple-xcap-12>):
>
> >    Before the server returns the 200 OK response to a DELETE, it MUST
> >    process the resource interdependencies as defined in Section 8.2.7.
> >    As long as the document still exists after the delete operation, any
> >    successful response to DELETE MUST include the entity tag of the
> >    document.
>
> Note that in this case, "document" does not refer to the thing
> identified by the request URI, but to hierarchy of URIs, identifying
> different parts of an XML document.
>
> So is it OK to return an ETag in response to a successful DELETE, when a
>   subsequent GET would return a 404?
>
> Best regards, Julian
>
>
Received on Sunday, 5 November 2006 17:56:19 GMT

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