[JCR-3535] Davex remoting should support absolute path hrefs

• Type: Improvement
• Status: Closed
• Priority: Major
• 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-jcr-server, jackrabbit-spi2dav
• Assignee: Julian Reschke
• Reporter: Timothee Maret
• Created: 18/Mar/13 12:43
• Updated: 10/May/13 19:44
• Resolved: 02/May/13 15:13

Description

JCR-1873 introduced an optional support for hrefs as absolute paths (instead of URIs).
This feature should also be supported by the Davex remoting (client side).

Issue Links

• is related to: JCR-3574 Leverage WebDAV compliance class 3 to use absolute paths in Destination header field

Sub-Tasks

• locator for RootCollection generates a broken href when using absolutePath setting: Closed
• header fields values such as "Location" need to be resolved against the request uri: Closed
• URIResolverImpl needs to handle absolute paths in addition to absolute URIs: Closed
• improve error logging for unexpected path formats: Closed
• RepositoryService.getReferences needs to deal with absolute paths in hrefs: Closed
• AbstractLocatorFactory.createResourceLocator needs to be called with an absolute URI as prefix: Closed
• use absolute paths in DeltaV request bodies, and resolve hrefs in responses properly: Closed
• JcrPrivilegeReport needs to deal with both absolute paths and absolute URIs in payloads: Closed
• UPDATE method needs to deal with both absolute paths and absolute URIs in payloads: Closed