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


From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 04 Nov 2006 11:38:24 +0100
Message-ID: <454C6DA0.5060301@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>


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 Saturday, 4 November 2006 10:38:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:40 UTC