You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2015/08/03 18:55:05 UTC

[jira] [Created] (JCR-3895) Add handle to handle webdav LOCK requests

Tobias Bocanegra created JCR-3895:
-------------------------------------

             Summary: Add handle to handle webdav LOCK requests
                 Key: JCR-3895
                 URL: https://issues.apache.org/jira/browse/JCR-3895
             Project: Jackrabbit Content Repository
          Issue Type: Bug
            Reporter: Tobias Bocanegra


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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)