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

["Satya Deep Maheshwari (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012484#comment-15012484 ] 

Satya Deep Maheshwari commented on JCR-3895:
--------------------------------------------

There has been no update on this since a long time. Can somebody please look into this and review the proposed implementation? 

> Add handler to handle webdav LOCK requests
> ------------------------------------------
>
>                 Key: JCR-3895
>                 URL: https://issues.apache.org/jira/browse/JCR-3895
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-jcr-server
>            Reporter: Tobias Bocanegra
>         Attachments: JCR-3895.patch
>
>
> 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)