[
https://issues.apache.org/jira/browse/SLING-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708840#action_12708840
]
Felix Meschberger commented on SLING-967:
-----------------------------------------
For the base Jackrabbit WebDAV servlet, I would have proposed an IOHandler. But
this has two drawbacks: (1) it would collide with the DirListingHandler and (2)
trying to use a special extension will not easily work.
Another option would be to overwrite the AbstractWebDavServlet.doGet method and
check for the .davmount extension if the resource does not exist and return the
dav mount response in this case....
Anyway, apart from the very simple core response generation, there is probably
nothing, which could be shared...
> Support davmount requests (RFC 4709)
> ------------------------------------
>
> Key: SLING-967
> URL: https://issues.apache.org/jira/browse/SLING-967
> Project: Sling
> Issue Type: New Feature
> Components: JCR
> Affects Versions: JCR Webdav 2.0.4
> Reporter: Felix Meschberger
>
> RFC 4709 [1] defines a file format and MIME type to convey WebDAV mount
> information from servers to clients.
> Generating such a response is easy for Sling in that the WebDAV support can
> register servlet responding to the "davmount" extension, which maps to the
> application/davmount+xml extension. This servlet would generate the correct
> response.
> For example a request to
> http://host/some/content.davmount
> might reply with
> <dm:mount xmlns:dm="http://purl.org/NET/webdav/mount";>
> <dm:url>http://host:80/</dm:url>
> <dm:open>some/content/</dm:open>
> </dm:mount>
> [1] http://www.ietf.org/rfc/rfc4709.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
