W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2002

Re: FW: 207 Multi-Status success

From: Joe Orton <joe@manyfish.co.uk>
Date: Wed, 24 Jul 2002 23:53:48 +0100
To: WebDAV <w3c-dist-auth@w3.org>
Message-ID: <20020724235348.A26860@light.plus.com>

> From: Bill Brown [mailto:billb@tibco.com]
> Sent: Wednesday, July 24, 2002 2:54 PM
> To: 'w3c-dist-auth@w3.org'
> Subject: [Moderator Action] 207 Multi-Status success
> 
> 
> I recently implemented the Dav protocol for our Schema repo so it is now a
> Dav server....wrote all the code to handle failures for lock, delete, move,
> copy and proppatch, so they return a 207 multi-status response and the
> appropriate xml as defined by the Dav spec.....my problem is that now.....I
> can't find a Dav client that recognizes 207 multi-status as a
> "failure"....everyone I've tried, treats it as a "success"....this actually
> makes sense to me, since 200 level status codes have always meant "success"
> to me....so, if I change the code to remap the 207 multi-status and return a
> 412 Precondition Failed....then all the clients will treat that response
> status as a failure.....obviously, since 400 level codes are "client error"
> responses......I don't have much choice but to leave it that way.....
> 
> Two questions....1) Am I completely missing something here?? and 2) Can
> anybody point me to a Dav client that treats the 207 multi-status as a
> "failure" in the appropriate cases??

cadaver (and any other client based on the neon library) treats a 207
response to MKCOL, DELETE, etc as an error.

Regards,

joe
Received on Wednesday, 24 July 2002 18:53:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:01 GMT