[JCR-3895] Add handler to handle webdav LOCK requests

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: jackrabbit-jcr-server
• Assignee: Unassigned
• Reporter: Tobias Bocanegra
• Created: 03/Aug/15 16:54
• Updated: 19/Nov/15 00:42

Description

similar to JCR-3884, an application should be able to control how LOCK requests are handled.

the concrete use case: WebDAV on OSX does not respect failing PUT requests, if the prior LOCK request succeeded.
in the case where a user does not have write access to a node, and the node does not have mix:lockable, the webdav server creates a in-memory lock token for that node, hence allowing the LOCK.

We don't want to change this behavior in general, as it might have unexpected results in other places, but to be able to control the LOCK behavior in more detail in a handler than can be controlled by the application.

workaround: create servlet filter

Issue Links

• blocks: SLING-4961 Add ability to handle webdav based LOCK/UNLOCK requests
• is related to: SLING-4825 Add ability to handle webdav based DELETE requests
• relates to: JCR-3884 Add handler to handle webdav based DELETE requests