[Issue 29152] webDAV locking needs to be implemented

[bu...@apache.org]

https://bz.apache.org/ooo/show_bug.cgi?id=29152

Berenice Carissa <be...@protonmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bernicecarisa@protonmail.co
                   |                            |m

--- Comment #122 from Berenice Carissa <be...@protonmail.com> ---
A WebDAV compliant server is not required to support locking in any form. If
the server does support locking it may choose to support any combination of
exclusive and shared locks for any access types.

DAV:lockdiscovery property

The DAV:lockdiscovery property returns a listing of who has a lock, what type
of lock he has, the timeout type, the time remaining on the timeout, the
associated lock token and the root of the lock. 

   <!ELEMENT lockdiscovery (activelock)* >

   <!ELEMENT activelock (lockscope, locktype, depth, owner?,
                         timeout?, locktoken?, lockroot) >

Depth: the value of the Depth header

   <!ELEMENT depth (#PCDATA) >

owner: provides information about the principal taking out a lock (see Section
2.5.5).

   <!ELEMENT owner ANY>

timeout: the time remaining until timeout of a lock.

   <!ELEMENT timeout (#PCDATA) >

locktoken: the lock token associated with a lock; the href element contains the
lock token.

   <!ELEMENT locktoken (href) >

lockroot: the URL that was specified as Request-URI in the LOCK creation
request; the href element contains the URL (see Section 2.5.3).

   <!ELEMENT lockroot (href) >

As discussed above, the principal authenticated for the UNLOCK request MUST be
allowed to remove the identified lock.

Thanks !!
http://qwikfix.co.uk/bt-customer-services-contact-number/

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are on the CC list for the issue.