-   Linux - Server (
-   -   webdav with Apache web server (

fatra2 07-09-2008 08:16 AM

webdav with Apache web server

I normally try to get around by trying for myself until I manage to get the trick. But this time, I am stump.

I have a web server, running with Apache. Part of this server serves as a calendar server (so that I am not late for any of my meetings, anywhere in the world!!!). Webdav is in charge of the calendar server.

I have to say everything seems to be working fine. I can load some calendars in my server. I can view them in thunderbird. Only the registered users have access to the calendars. The situations seems to be under control.

The problem comes, when I try to change the calendar from thunderbird-lightning. I am not able to make any modification on the calendars, eventhough I am a registered user.

I have the webdav module configured

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

with the

<Location /cal/>
        DAV On
        AuthType Basic
        AuthName "Calendar Restricted to registered users"
        AuthUserFile /etc/httpd/passwd/passwords
        require user webdav

The funny thing is that I can access the files with tools like cadaver, to change the name of the calendars.

I just cannot change the change the content of the files, from thunderbird.

Any idea would be truly helpful.


fatra2 07-11-2008 01:31 AM

Hi there,

I still did not manage to have that webdav working.

Maybe if I give a little more detail. Since last time, I made many more research to solve this problem. I believe the problem comes from the certificate. The request made by lightning does not seems to match the server's certificate.

Maybe someone can help me on how to create a local certificate that would allow me to connect to webdav correctly???


fatra2 07-12-2008 03:43 AM

Hi there,

Just to keep this post up to date, I manage to work around my problem. I had everything setup right, with the correct certificate. I just had some security modules that were protecting the write access to the files. Instead of going round and round into which is doing what, I just erased them from. I know it's not the best way to do things, but I had enough of mingling with this.

I erased all the security modules (mod_*) in the /etc/httpd/conf.d/ directory. It seems to work. And the security seems to be quite ok, as well.


All times are GMT -5. The time now is 03:29 PM.