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

Re: WebDAV sync report w/invalid sync token

From: Evert Pot <evert@rooftopsolutions.nl>
Date: Tue, 15 Nov 2011 16:32:52 +0100
Cc: Ken Murchison <murch@andrew.cmu.edu>, w3c-dist-auth@w3.org
Message-Id: <05D525B7-5691-4EED-82E9-45CE010C12E1@rooftopsolutions.nl>
To: Cyrus Daboo <cyrus@daboo.name>

On 2011-11-15, at 4:13 PM, Cyrus Daboo wrote:

> Hi Ken,
> 
> --On November 15, 2011 10:06:45 AM -0500 Ken Murchison <murch@andrew.cmu.edu> wrote:
> 
>>> I prefer to return 403's for all errors that involve pre-conditions and
>>> that contain the DAV:error element.
>> 
>> Thanks Cyrus.
>> 
>> 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.
> 
> 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
Received on Tuesday, 15 November 2011 15:33:27 GMT

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