You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2008/01/31 17:29:08 UTC
[jira] Created: (JCR-1352) illegal format for WebDAV lock tokens
illegal format for WebDAV lock tokens
-------------------------------------
Key: JCR-1352
URL: https://issues.apache.org/jira/browse/JCR-1352
Project: Jackrabbit
Issue Type: Bug
Components: jackrabbit-webdav
Reporter: Julian Reschke
Priority: Minor
WebDAV lock tokens are URIs, while JCR lock tokens aren't. Therefore, the WebDAV servlet needs to transform outgoing JCR lock tokens (response headers and WebDAV properties) into URI format, and needs to parse the original lock token out of incoming WebDAV lock tokens (in request headers).
Proposed mapping:
- when the JCR lock token uses UUID format, use "urn:uuid",
- otherwise encode with a constant prefix, such as "tag:jackrabbit.apache.org,2008:LockTokens."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1352) illegal format for WebDAV lock tokens
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-1352:
------------------------
Component/s: (was: jackrabbit-webdav)
jackrabbit-jcr-server
adjust component.
> illegal format for WebDAV lock tokens
> -------------------------------------
>
> Key: JCR-1352
> URL: https://issues.apache.org/jira/browse/JCR-1352
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-jcr-server
> Reporter: Julian Reschke
> Priority: Minor
>
> WebDAV lock tokens are URIs, while JCR lock tokens aren't. Therefore, the WebDAV servlet needs to transform outgoing JCR lock tokens (response headers and WebDAV properties) into URI format, and needs to parse the original lock token out of incoming WebDAV lock tokens (in request headers).
> Proposed mapping:
> - when the JCR lock token uses UUID format, use "urn:uuid",
> - otherwise encode with a constant prefix, such as "tag:jackrabbit.apache.org,2008:LockTokens."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1352) illegal format for WebDAV lock tokens
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565694#action_12565694 ]
angela commented on JCR-1352:
-----------------------------
i don't have any preference. the only thing you have to make sure is the following:
the lock tokens obtained from the request are added to the jcr-Session obtained to handle the request. If the lock token has been modified in order make it compliant with whatever requiment form rfc 2518, you must revert the modification before you add the token to the session. otherwise you won't ever be able to become lock holder (i.e. Session.addLockToken(String) failes without further notice... only a warning in the log file).
> illegal format for WebDAV lock tokens
> -------------------------------------
>
> Key: JCR-1352
> URL: https://issues.apache.org/jira/browse/JCR-1352
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-webdav
> Reporter: Julian Reschke
> Priority: Minor
>
> WebDAV lock tokens are URIs, while JCR lock tokens aren't. Therefore, the WebDAV servlet needs to transform outgoing JCR lock tokens (response headers and WebDAV properties) into URI format, and needs to parse the original lock token out of incoming WebDAV lock tokens (in request headers).
> Proposed mapping:
> - when the JCR lock token uses UUID format, use "urn:uuid",
> - otherwise encode with a constant prefix, such as "tag:jackrabbit.apache.org,2008:LockTokens."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.