Re: WebDAV sync report w/invalid sync token

Evert Pot <[email protected]> Tue, 15 Nov 2011 16:32:52 +0100
Newsgroups gmane.ietf.webdav
Message-ID <[email protected]>
On 2011-11-15, at 4:13 PM, Cyrus Daboo wrote:

> Hi Ken,
>=20
> --On November 15, 2011 10:06:45 AM -0500 Ken Murchison =
<[email protected]> wrote:
>=20
>>> I prefer to return 403's for all errors that involve pre-conditions =
and
>>> that contain the DAV:error element.
>>=20
>> Thanks Cyrus.
>>=20
>> I can see the logic there.  So we want to tell the client to not =
repeat
>> the request with the same sync-token as opposed to telling it that =
the
>> request may work as-is once some other unspecified conflict is =
resolved.
>=20
> Well any client using the sync REPORT should be looking at the =
DAV:error element and the behavior for that is explicitly described in =
the spec. If DAV:error were not present, then the client would follow =
the "normal" rules for HTTP status code processing.

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.

Evert=