Zimbra WebDAV

[bmw]

Researching the PHP modules for Apache on CentOS 5 for WebDAV and how it controls the communication, I did a search for all the HTTPD.CONF files that configure WebDAV.

I found these results:
WebDAV for Zimbra

/etc/httpd/conf/httpd.conf
175 LoadModule dav_module modules/mod_dav.so

179 LoadModule dav_fs_module modules/mod_dav_fs.so


549 # WebDAV module configuration section.
550 #
551 <IfModule mod_dav_fs.c>
552     # Location of the WebDAV lock database.
553     DAVLockDB /var/lib/dav/lockdb
554 </IfModule>

884 # The following directive disables redirects on non-GET requests for
885 # a directory that does not include the trailing slash.  This fixes a
886 # problem with Microsoft WebFolders which does not appropriately handle
887 # redirects for folders with DAV methods.
888 # Same deal with Apple's DAV filesystem and Gnome VFS support for DAV.
889 #
890 BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
891 BrowserMatch "MS FrontPage" redirect-carefully
892 BrowserMatch "^WebDrive" redirect-carefully
893 BrowserMatch "^WebDAVFS/1.[0123]" redirect-carefully
894 BrowserMatch "^gnome-vfs/1.0" redirect-carefully
895 BrowserMatch "^XML Spy" redirect-carefully
896 BrowserMatch "^Dreamweaver-WebDAV-SCM1" redirect-carefully


/opt/zimbra/conf/httpd.conf
959 # The following directive disables redirects on non-GET requests for
960 # a directory that does not include the trailing slash.  This fixes a
961 # problem with Microsoft WebFolders which does not appropriately handle
962 # redirects for folders with DAV methods.
963 # Same deal with Apple's DAV filesystem and Gnome VFS support for DAV.
964 #
965 BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
966 BrowserMatch "^WebDrive" redirect-carefully
967 BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
968 BrowserMatch "^gnome-vfs" redirect-carefully


/opt/zimbra/httpd-2.2.15/conf/httpd.conf 
394 # Distributed authoring and versioning (WebDAV)
395 #Include conf/extra/httpd-dav.conf


/opt/zimbra/httpd-2.2.15/conf/original/httpd.conf 
393 # Distributed authoring and versioning (WebDAV)
394 #Include conf/extra/httpd-dav.conf

Questions:

1. There is no "DAVLockDB /var/lib/dav/lockdb" file being created. lockdb doesn't exist. Should it?
2. Should "conf/extra/httpd-dav.conf" file be turned on for WebDAV to work? It's commented out.

Please advise. Thanx in advance.

[jummo]

IMHO the WebDAV protocol is handled by the Zimbra mailboxd service and not the Apache HTTPD. Therefore you can't configure WebDAV through httpd.conf files. Futhermore the /etc/httpd/conf/httpd.conf is independent from Zimbra.

Some useful links to get WebDAV working
* WebDAV - Zimbra :: Wiki
* Ajcody-WebDAV - Zimbra :: Wiki

[bmw]

@jummo Can you expand on why you think WebDAV is handled there? Do you have any solutions/ideas as to why WebDAV on Macintosh continues to lose its connection so that open/edit/save doesn't work?

Also, why are there httpd.conf files in the Zimbra folder?

Thanx in advance.

IMHO the WebDAV protocol is handled by the Zimbra mailboxd service and not the Apache HTTPD. Therefore you can't configure WebDAV through httpd.conf files. Futhermore the /etc/httpd/conf/httpd.conf is independent from Zimbra.

Some useful links to get WebDAV working
* WebDAV - Zimbra :: Wiki
* Ajcody-WebDAV - Zimbra :: Wiki

[uxbod]

No httpd.conf files as it is all handled by Jetty.

[bmw]

No httpd.conf files as it is all handled by Jetty.

Hmmm...Okay, so then the httpd.conf files are preconfigured.

Then, moving forward, WebDAV continues to be broken when performing open/edit/save function. Zimbra WebDAV loses its connection and then proceeds to delete or overwrite the file depending on what application being used, ie, MS-Word, OpenOffice, etc.

Zimbra support and developers have not produced a solution or fix for this in two years. I am being forced by my superiors to seek another solution despite my continued support for the product. I am considering trying to fold Alfresco into an iframe tab.

But, (the all inclusive Zimbra administrators) we shouldn't have to go through these pains and lose an integrated component of the collaborative product.

Any ideas?