W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2011

Re: WebDAV sync report w/invalid sync token

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 15 Nov 2011 17:31:39 +0100
Message-ID: <4EC293EB.8070508@gmx.de>
To: Cyrus Daboo <cyrus@daboo.name>
CC: Evert Pot <evert@rooftopsolutions.nl>, Ken Murchison <murch@andrew.cmu.edu>, w3c-dist-auth@w3.org
On 2011-11-15 17:23, Cyrus Daboo wrote:
> Hi Julian,
>
> --On November 15, 2011 5:02:04 PM +0100 Julian Reschke
> <julian.reschke@gmx.de> wrote:
>
>>> I'd be nice if the spec authors could explicitly state an http error
>>> code for every error condition. I don't think leaving it open to
>>> interpretation (or unclear.. have your pick) is a good thing. ...
>>
>> That can be dangerous, as it could trick developers to think that these
>> are the only codes that need to be handled... So the spec would need to
>> make clear that these are just examples/suggestions...
>
> Which is exactly what the WebDAV base spec describes for
> pre-/post-conditions, hence the fact that no other WebDAV extension
> documents explicitly list a status code. Plus the distinction between
> some codes is not always clear - we could argue for a long time over
> whether 403 or 409 should be returned for an invalid sync token.

Indeed; the HTTP status code mainly is for components that do not know 
about WebDAV. Those who do should inspect DAV:error.

Best regards, Julian
Received on Tuesday, 15 November 2011 16:32:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 November 2011 16:32:15 GMT