W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2003

RE: Using If and not failing

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 1 Feb 2003 10:57:35 +0100
To: "Lisa Dusseault" <lisa@xythos.com>, "'Webdav WG'" <w3c-dist-auth@w3c.org>
Message-ID: <JIEGINCHMLABHJBIGKBCCEOPGFAA.julian.reschke@gmx.de>

Lisa,

you are aware that this exactly the proposal that Geoff and myself have been
making for some months now?

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Lisa Dusseault
> Sent: Saturday, February 01, 2003 7:15 AM
> To: 'Lisa Dusseault'; 'Webdav WG'
> Subject: RE: Using If and not failing
>
>
>
>
> I've been looking into this some more. This trick should also work with
> tagged lists.  However, since multiple tagged lists are ANDed together
> (" If the state of the resource to which the header is applied does not
> match any of the specified state lists then the request MUST fail") it
> has to be done a little differently.
>
> <no-lock> here represents a lock token that the client made up, which is
> intended to Fail.
> If: <href1> (<locktoken1> Not <no-lock>) <href2> (<locktoken2> Not
> <no-lock>)
>
> This evaluates as
> 	((href1 matches locktoken1) OR NOT (href1 matches no-lock))
> 	AND  ((href2 matches locktoken2) OR NOT (href2 matches no-lock))
>
> I tested this against Xythos WFS, and clients can use this syntax to
> make sure that the request does not fail even if locktoken1 or
> locktoken2 are no longer there.  Of course this should always be used
> with ETag checks.
>
> lisa
>
>
> > -----Original Message-----
> > From: Lisa Dusseault [mailto:lisa@xythos.com]
> > Sent: Thursday, January 23, 2003 12:20 PM
> > To: Webdav WG
> > Subject: Using If and not failing
> >
> >
> >
> >
> > Did anybody point out that there's an interesting way for the
> > client to
> > ensure that the If header never fails the request, by always
> > providing a
> > "true" statement?
> >
> > -          One or more tokens can be put in parentheses to
> > form a group
> > or list
> > -          Multiple lists can be included and they are ORed together
> >
> > So if the client wants to put a bunch of locktokens in the If
> > header it
> > can put any number of them in there, all separated by virtual "OR"s:
> >
> > DOSTUFF /resourceurl.html HTTP/1.1
> > If: (<locktoken1>) (<locktoken2>) (<locktoken3)
> >
> > This request will succeed if the any of the clauses match.
> >
> >
> >
> >
>
>
Received on Saturday, 1 February 2003 04:57:59 GMT

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