Hey guys, I need to publish / share a calendar, so I am looking at webdav. This is a CentOS4 / Apache2 box with the following settings;

httpd.conf;
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule dav_module modules/mod_dav.so

# WebDAV module configuration section.
#
<IfModule mod_dav_fs.c>
# Location of the WebDAV lock database.
DAVLockDB /var/lib/dav/lockdb
</IfModule>

The vhosts file has;
<Directory /home/person/websites/domain.com/htdocs/WEBdav/>
DAV On
AuthType Basic
AuthName "WebDAV Restricted"
AuthUserFile /usr/local/passwords
Require user username
</Directory>
</VirtualHost>

Going to publish calendar, or even browser, if I hit that URL, I get the popup, successful auth but the calendar never publishes.

Thanks.

What do your logs indicate? Sounds more like a calendar problem than WebDAV issue at this time.

I am having a lot of problems getting dav to work...I set it up and it worked on core 7...I updated the server and then it stopped and have not been able to find out why...if you find a solution, let me know...

I used the same config as above,

Vhosts shows;
<Directory "/home/user/websites/domain.com/htdocs/WEBdav/user">
DAV On
AuthType Basic
AuthName "WebDAV Restricted"
AuthUserFile /usr/local/passwords
Require user myuser
</Directory>

Then what I did was create a blank file (touch mycal.ics), made sure apache had access to read/write to that file. Then using thunderbird (lightning plugin) or sunbird, subscribed to that caledar and it worked perfect.

Hope you have the same luck.

I found an issue with mod_security. in my webdav settings, it was blocking me. i have to disable a couple of the rules in order to get my dav working but it did work. where i found it was in my log under httpd error log. i do not know if it is the same problem but this was the fix..

IfModule mod_security2.c>
SecRuleRemoveById set the problem rules here
</IfModule>

I do not like to do this but it was the only way I could get dav working...this should go in your httpd.conf file...

the key was finding the error in your httpd error log file and figuring out that it was modsecurity that was doing it.

baldur