[
https://issues.apache.org/jira/browse/OAK-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856005#comment-15856005
]
Julian Reschke commented on OAK-5501:
-------------------------------------
I just tried and it seems to work for me.
The code initializes both servlets -- are you connecting to the right one? ->
http://localhost:8080/repository/default
> 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.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)
