On 2017-01-23 13:07, mathiasconradt wrote:
Why does the WebDAV implementation/behaviour of Jackrabbit2 and Oak differ so
much? 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. What's the
reason for this different implementation?
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.
Screenshots taken from the standalone-jars of each:
https://snag.gy/NQEqaP.jpg
Regards,
Mathias
They are not supposed to differ like that.
Jackrabbit has two WebDAV modes, one used for standard WebDAV clients,
one for remoting. For some reason you see the former on Jackrabbit and
the latter on Oak.
This sounds as if the Oak standalone has a config/setup problem...
Best regards, Julian
