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 "Mathias Conradt (JIRA)" <ji...@apache.org> on 2017/01/23 13:52:26 UTC
[jira] [Updated] (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 ]
Mathias Conradt updated OAK-5501:
---------------------------------
Description:
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 the default 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!
was:
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 the default 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
> 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.6
> Reporter: Mathias Conradt
> Priority: Minor
>
> 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 the default 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.4#6332)