To enable mod_dav, add the following to a container in your
Also, specify a valid filename for the DAV lock database by adding the following to the global section in your
DavLockDB /tmp/DavLock (Any web-server writeable filename, without an extension)
Dav directive to enable the WebDAV HTTP methods
for the given container.
You may wish to add a
clause inside the
directive to limit access to DAV-enabled locations.
DavLockDB directive to specify the full path to the
lock database, excluding an extension. The default (file system)
implementation of mod_dav uses a SDBM database to track user locks.
modules/dav/util/lockview can be
used from the server to display all locks in a lock database.
When a client requests a DAV resource lock, it can also specify a time when the lock will be automatically removed by the server. This value is only a request, and the server can ignore it or inform the client of an arbitrary value.
DavMinTimeout directive to specify, in seconds,
the minimum lock timeout to return to a client. Microsoft Web Folders
defaults to a timeout of 120 seconds; the
can override this to a higher value (like 600 seconds) to reduce the chance
of the client losing the lock due to network latency.
DavDepthInfinity directive to allow the processing
of PROPFIND requests containing the header 'Depth: Infinity'.
Because this type of request could constitute a denial-of-service attack,
by default it is not allowed.
LimitXMLRequestBody directive to limit the
size of an XML request which mod_dav will attempt to parse. Specify
a size greater than zero.