jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Porath" <rol...@exari.com>
Subject RE: webdav lock tokens
Date Thu, 21 Feb 2008 00:15:37 GMT
Hi brad

Hope this helps
https://issues.apache.org/jira/browse/JCR-1352

cheers

roland

> -----Original Message-----
> From: bradmoody@gmail.com [mailto:bradmoody@gmail.com] On Behalf Of Brad
> Sent: Thursday, 21 February 2008 3:52 AM
> To: users@jackrabbit.apache.org
> Subject: webdav lock tokens
> 
> Hi,
> 
> we're running some tests where we are locking a directory before we
> write a file an unlock after the write is complete. After
> investigating a problem we've been having, we've noticed that
> sometimes we get an "opaque" lock token from the server. Normally we
> get something like this:
> 
> <D:prop
> xmlns:D="DAV:"><D:lockdiscovery><D:activelock><D:lockscope><D:exclusive/><
> /D:lockscope><D:locktype><D:write/></D:locktype><D:depth>0</D:depth><D:tim
> eout>Second-
> 2147483</D:timeout><D:owner>Admin</D:owner><D:locktoken><D:href>29001f9b-
> 1aaa-4252-9fae-9d9d9b2c14a8-
> 3</D:href></D:locktoken></D:activelock></D:lockdiscovery></D:prop>
> 
> ...but every so often we get this:
> 
> <D:prop
> xmlns:D="DAV:"><D:lockdiscovery><D:activelock><D:lockscope><D:exclusive/><
> /D:lockscope><D:locktype><D:write/></D:locktype><D:depth>0</D:depth><D:tim
> eout>Second-20</D:timeout><D:locktoken><D:href>opaquelocktoken:4ad983e1-
> a1ec-4304-8879-
> 91b263adfd4a</D:href></D:locktoken></D:activelock></D:lockdiscovery></D:pr
> op>
> 
> Which is bad when we attempt the unlock as the server returns a HTTP
> 419 Locked.
> 
> Anyway, I guess my question is do we need to do something extra with
> this token? We've looked in the WebDAV spec and are none the wiser as
> to what it means and why we are getting a different token format.
> 
> Thanks,
> Brad.
> 
> !DSPAM:47bc5ac4304641420419767!



Mime
View raw message