[JCR-3574] Leverage WebDAV compliance class 3 to use absolute paths in Destination header field

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4.3, 2.6, 2.7
• Fix Version/s: 2.4.4, 2.6.1, 2.7
• Component/s: jackrabbit-spi2dav
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 18/Apr/13 13:04
• Updated: 10/May/13 19:44
• Resolved: 18/Apr/13 16:12

Description

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).

Issue Links

• is related to: JCR-3575 use absolute paths in WebDAV request bodies (DAV:href elements)
• relates to: JCR-3535 Davex remoting should support absolute path hrefs