You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2017/05/30 08:39:16 UTC
[jira] [Closed] (OAK-5501) Oak Standalone: Webdav configuration is
set to remoting mode by default
[ https://issues.apache.org/jira/browse/OAK-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella closed OAK-5501.
---------------------------------
Bulk close for 1.7.0
> Oak Standalone: Webdav configuration is set to remoting mode by default
> -----------------------------------------------------------------------
>
> Key: OAK-5501
> URL: https://issues.apache.org/jira/browse/OAK-5501
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: examples, webapp
> Affects Versions: 1.5.18
> Reporter: Mathias Conradt
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.7.0, 1.8
>
>
> The *Oak Standalone WebDAV configuration* is set to *remoting mode* by default, but I would expect it to be in the same mode as the *Jackrabbit2 (= mode for standard WebDAV clients)*:
> When I connect to a Jackrabbit2 repo via WebDAV, I see the files as binary content and can access the binary content, i.e. open a pdf directly from there.
> When connecting to an Oak repo via WebDAV though, the content nodes (i.e. when I post/upload a pdf or jpg via WebDAV) are represented as folders, the binary content is not directly accessible via WebDAV client.
> I would expect that most WebDAV users would like to access the binary content (jcr:content/jcr:data) of a repo rather than seeing the node hierarchy, and therefore *Oak's default WebDAV mode should also be the one for standard WebDAV clients*.
> Screenshots taken from the standalone-jars of each, after I started them each via {{java -jar /path/to/standalone.jar}}: https://snag.gy/NQEqaP.jpg
> !https://snag.gy/NQEqaP.jpg!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)