jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3633) If header field sent with PROPFIND (for lock discovery)
Date Mon, 29 Jul 2013 15:05:48 GMT

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

Julian Reschke commented on JCR-3633:
-------------------------------------

Interesting enough, the fix seems to break 2.4. Investigating.
                
> If header field sent with PROPFIND (for lock discovery)
> -------------------------------------------------------
>
>                 Key: JCR-3633
>                 URL: https://issues.apache.org/jira/browse/JCR-3633
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-spi2dav
>    Affects Versions: 2.4.4, 2.6.3, 2.7
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 2.4.5, 2.6.4, 2.7.1
>
>         Attachments: JCR-3633.diff
>
>
> RepositoryServiceImpl.getLockInfo() sends a PROPFIND request including an If header field
containing all lock tokens owned by the session. This will fail (with Precondition Failed)
unless there's only one lock token, and the request URI happens to be the one of the lock
with the specified lock token.
> (This is probably a leftover from a time where the transient space wasn't yet managed
using the "Transaction" header field).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message