Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to enable HTTP-DAV on Apache (httpd.x86_64 2.2.3-43.el5.centos) running on CentOS 5.4.

I have the following relevant entries in my httpd.conf

LoadModule dav_module modules/
LoadModule dav_fs_module modules/

<IfModule mod_dav_fs.c>    
    DAVLockDB /var/lib/dav/lockdb

<Location /var/www/html/updates>
    Dav On

/var/www/html/ is the apache root. I have reloaded apache without any errors in the error log. I can also access this dir via HTTP in Firefox

I have an application under development which needs to communicate with the web server over HTTP-DAV but instead reports that the web server returned "(405) Method not allowed". This happens when it sends a PROPFIND request.

Apache's access log reports the following when that happens - - [25/Nov/2010:17:21:26 +0200] "PROPFIND /updates/ HTTP/1.1" 405 320 "-" "-"

Presumably HTTP-DAV isn't enabled. What am I doing wrong?

Edit in reply to pacey: There are no Limit or LimitExcept Directives in any of apache's conf files. There is no .htaccess file in /var/www/html/updates/ or /var/www/html/

Edit in reply to Zoredache: Apache has write access to updates

Edit in reply to iiegn: I gave cadaver a try. Apparently WebDAV's not enabled.

dav:!> open http://hybrid/updates/
Could not access /updates/ (not WebDAV-enabled?):
405 Method Not Allowed
Connection to `hybrid' closed.

The only relevant thing in the logs (LogLevel debug) is in the access log: - - [26/Nov/2010:14:41:45 +0200] "OPTIONS /updates/ HTTP/1.1" 200 - "-" "cadaver/0.22.3 neon/0.25.5" - - [26/Nov/2010:14:41:45 +0200] "PROPFIND /updates/ HTTP/1.1" 405 319 "-" "cadaver/0.22.3 neon/0.25.5"
share|improve this question
are there any <Limit> or LimitExcept Directives in the apache configuration? – pacey Nov 25 '10 at 15:50
maybe the error log will tell you more? – Mike Nov 25 '10 at 16:04
Does the apache user have write access to /updates/? – Zoredache Nov 25 '10 at 21:21
is there a .htaccess file in the path to /var/www/html/updates which gets evaluated? If so, what are the contents. – pacey Nov 26 '10 at 9:30
up vote 5 down vote accepted

Finally figured it out

Instead of

<Location /var/www/html/updates>
    Dav On

it needs to be

<Directory /var/www/html/updates>
   Dav On
share|improve this answer
hm, then there seems to be some interaction with, i guess, /var/www being DocRoot or other (Directory) settings further up the path. i have dav working on a <Location /some/path> with /some/path not being part of any other setting. – iiegn Nov 26 '10 at 13:51
I have the same problem (405 error) but I am using Directory. – Brad Aug 4 '11 at 18:37
Thanks - this helped me too. – Lord Loh. Feb 1 '12 at 21:53
DAV will not work on a directory if DirectoryIndex is enabled and the index file exists (usually index.html). I guess the two situations require different responses for the same HTTP request. – migle Oct 10 '15 at 18:08
This worked, but I don't understand why... The docs specify the use of mod_dav with Location tags... – regulatre Dec 7 '15 at 20:52

the set-up seems sufficient.

to test the set-up you could try cadaver, the command-line WebDAV client for Unix: . there, start with something like "> open URL" to see whether you can open a connection. then, "> propget ." or "> ls"

...and with the PROPFIND request pay attention to:

share|improve this answer
+1 for suggesting cadaver – Manos Dilaverakis Nov 26 '10 at 13:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.