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 2013/04/18 18:13:16 UTC
[jira] [Updated] (JCR-3574) Leverage WebDAV compliance class 3 to
use absolute paths in Destination header field
[ https://issues.apache.org/jira/browse/JCR-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated JCR-3574:
--------------------------------
Summary: Leverage WebDAV compliance class 3 to use absolute paths in Destination header field (was: leverage WebDAV 3 compliance class to use absolute paths in Destination header field)
> Leverage WebDAV compliance class 3 to use absolute paths in Destination header field
> ------------------------------------------------------------------------------------
>
> Key: JCR-3574
> URL: https://issues.apache.org/jira/browse/JCR-3574
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-spi2dav
> Affects Versions: 2.4.3, 2.6, 2.7
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.4.4, 2.6.1, 2.7
>
>
> For the Destination header field in COPY and MOVE, the client should send absolute paths (instead of full URIs) iff the remote server identifies itself as being class 3 compliant (http://www.greenbytes.de/tech/webdav/rfc4918.html#compliance-class-3).
> This will work around problems when the remote server is behind an intermediate that rewrites the authority part of the URI (scheme/host/port).
--
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