Page 1 of 1

WebDAV Connection Error

PostPosted:Mon Aug 29, 2011 8:01 pm
by acekid
When trying to connect to webdav I get the following when using WebDrive:
webdav-error.jpg
webdav-error.jpg (95.31 KiB) Viewed 2860 times
Here is a screen shot from my config, jboss has been restarted... get the same error whether system.webdav.fix is on or off...
config-webdav.jpg
config-webdav.jpg (37.56 KiB) Viewed 2860 times
System Info
OpenKM 5.1.7
Ubuntu 10.04 LTS (Server 32bit)

Thanks!

Re: WebDAV Connection Error

PostPosted:Tue Aug 30, 2011 4:00 pm
by jllort
Which url are you using for webdav ? I suggest try first directly the url with firefox if url is correct will demand to you user and pass.

Re: WebDAV Connection Error

PostPosted:Wed Dec 07, 2011 7:53 pm
by Sascha
jllort wrote:Which url are you using for webdav ? I suggest try first directly the url with firefox if url is correct will demand to you user and pass.
That´s the first milestone to get WebDAV with OpenKM running! Since 5.1.8 the WebDAV-Url changes.

Secondly the wiki-Post http://wiki.openkm.com/index.php/WebDAV_access is a bit confusing, because the
  • system.webdav.server=on
must be changed in the Administration -> Configuration of OKM and not in the OpenKM.cfg

Thirdly not every WebDAV-Client works simple. In my case Webdrive rocks, NetDrive has some unknown connection-issues, BitKinex connects directly but has probs with directory-ranges and user-rights. I also tested DAVExplorer - very nice - but the datahandling is still like in OKM - nothing for big numbers.

Re: WebDAV Connection Error

PostPosted:Wed Dec 21, 2011 12:40 pm
by pavila
I have improved the http://wiki.openkm.com/index.php/WebDAV_access, sorry for the confusion.

WebDAV is a protocol which is error-prone because not every clients and server implements it in the same way. I don't understan why there are lots of problems depending on the clientm but in the Real World, this seems to be usual.

We changed the WebDAV implementation to improve client compatibility and now works better, but I know it is not perfect. We will keep improving it thnaks to the user feedback.

Please, tell me exactly the OpenKM version (and build) you are using and the neccesary steps to reproduce the issue. Keep on mind that you should use OpenKM-5.1.8 (final) and not a SNAPSHOT previous to the final release.

Regards.