Page 1 of 1

Webdav server configuration issue, Class 1 to Class 2

PostPosted:Thu Aug 01, 2013 7:47 am
by dun1982
Hi,
I'm currently evaluating OpenKM for our document management system and I have a problem with the webdav-service. For some reason, I cannot get the webdav to work without external client in Windows or Mac systems in write mode. With Mac OS X the problem is that the OpenKM Community edition 6.2.4 shows up as Class 1 compliant WebDAV server. Is there any way to configure it to work as Class 2, so I could be using the webdav folder directly with Finder like Dropbox folder?

This page do not offer that much help either regarding this topic: http://wiki.openkm.com/index.php/WebDAV_access

Is there something that I have missed?

I'm running OpenKM Community edition in Oracle Enterprise Linux 6.4.0 x64 (tomcat details):
Server version: Apache Tomcat/7.0.27
Server built: Mar 31 2012 03:43:36
Server number: 7.0.27.0
OS Name: Linux
OS Version: 2.6.39-400.21.2.el6uek.x86_64
Architecture: amd64
JVM Version: 1.6.0_34-b04
JVM Vendor: Sun Microsystems Inc.

Re: Webdav server configuration issue, Class 1 to Class 2

PostPosted:Mon Aug 12, 2013 8:33 am
by pavila
The information at http://wiki.openkm.com/index.php/WebDAV_access talk basically about Windows because most of our customers use Windows. There is a little part where talks about using WebDAV with MacOSX but we don't any Applet machine to test.

Re: Webdav server configuration issue, Class 1 to Class 2

PostPosted:Mon Aug 12, 2013 8:48 am
by dun1982
Ok, it seems the reason why Mac OS X sees the Webdav service in OpenKM as a class 1, is that it does not offer DAV LOCK-feature. In windows world this is not an issue, because the filesystem (NTFS) is handled differently than in POSIX-based system in general (*BSD, *NIX). But if you can implement that dav lock feature, I can then test the specific snapshot for you (just limit the differences only for webdav-protocol/service).

See: http://developer.apple.com/library/mac/ ... dav.8.html
"-o Options passed to mount(2) are specified with the -o option followed by a comma-separated string of options. See the mount(8) man page for possible options and their meanings. If connecting to a Class 1 compliant WebDAV server, the rdonly option will be set even if it was not specified because mount_webdav will not allow files to be opened with write access on servers which do not support the DAV LOCK method."

Re: Webdav server configuration issue, Class 1 to Class 2

PostPosted:Tue Aug 13, 2013 11:25 am
by pavila
We use Milton WebDAV library to implement the WebDAV interface to OpenKM repository. The current version we used in OpenKM is no more online because the maintainer took the decision of closing the source code. The new payment version has many features and enhancement but we can't include it in OpenKM Community because of license problems.

WebDAV protocol is a nightmare because every client implement the protocol in a different way and there are lots of incompatibility issues. We have centred in our most common customer which use Windows. We would like to support more systems and clients, but it is simply a number problem. Anyway, as said many times, we are open to contributions which fix problems or add features. Sadly people don't want to invest time on it, but want we do it for themself and for free.

We are currently involved in a CMIS implementation, but won't be included in the Community version until a couple of month (I think, but not sure). We have been having problems with people using Community version because they think we do not make a good support in a product that nobody pays. For this reason we don't want to include more features because they may cause problems.