Re: WebDAV sync report w/invalid sync token

Julian Reschke <[email protected]> Tue, 15 Nov 2011 17:31:39 +0100
Newsgroups gmane.ietf.webdav
Message-ID <[email protected]>
On 2011-11-15 17:23, Cyrus Daboo wrote:
> Hi Julian,
>
> --On November 15, 2011 5:02:04 PM +0100 Julian Reschke
> <[email protected]> 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