Re: DELETE and ETag

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 UTC