Modules | Directives | FAQ | Glossary | Sitemap | Report a bug
Apache HTTP Server Version 2.5
| Description: | Filesystem provider for mod_dav |
|---|---|
| Status: | Extension |
| Module Identifier: | dav_fs_module |
| Source File: | mod_dav_fs.c |
This module requires the service of mod_dav . It acts as a support module for mod_dav and provides access to resources located in the
server's file system. The formal name of this provider is
filesystem. mod_dav backend providers
will be invoked by using the Dav
directive:
Dav filesystem
Since filesystem is the default provider for
mod_dav , you may simply use the value
On instead.
| Description: | Location of the DAV lock database |
|---|---|
| Syntax: | DavLockDB file-path |
| Default: | DavLockDB DEFAULT_REL_STATEDIR/davlockdb |
| Context: | server config, virtual host |
| Status: | Extension |
| Module: | mod_dav_fs |
| Compatibility: | No default prior to version 2.5.1. |
Use the DavLockDB directive to specify
the full path to the lock database, excluding an extension. If the
path is not absolute, it will be taken relative to ServerRoot . The implementation of
mod_dav_fs uses a database to track user
locks. The type of database file can be changed using
DavLockDBType .
DavLockDB var/DavLock
The directory containing the lock database file must be
writable by the User
and Group under which
Apache is running. For security reasons, you should create a
directory for this purpose rather than changing the permissions on
an existing directory. In the above example, Apache will create
files in the var/ directory under the ServerRoot with the base filename
DavLock and extension name chosen by the server.
In httpd version 2.5.1 and later, a hard-coded default path
relative to the state directory (configurable via DefaultStateDir ) is used.
| Description: | Database type of the DAV lock database |
|---|---|
| Syntax: | DavLockDBType dbm-type |
| Default: | DavLockDBType default |
| Context: | server config, virtual host |
| Status: | Extension |
| Module: | mod_dav_fs |
| Compatibility: | Available in version 2.5.1 and later. |
Use the DavLockDBType directive to
specify the type of the database file. If the directive is not
used, the apr_dbm hard-coded default database type is
used, which is equivalent to using DavLockDBType default.
| Description: | Enable lock discovery |
|---|---|
| Syntax: | DavLockDiscovery on|off |
| Default: | DavLockDiscovery on |
| Context: | server config, virtual host, directory, .htaccess |
| Status: | Extension |
| Module: | mod_dav_fs |
| Compatibility: | Available from Apache 2.5.0 and later. |
DavLockDiscovery controls if the lock
discovery feature is enabled for PROPFIND method.
When disabled, PROPFIND always returns an empty
lockdiscovery section. This improves performance
if clients use PROPFIND a lot.
DavLockDiscovery off
| Description: | Set usage quota |
|---|---|
| Syntax: | DavQuota Off | None | #bytes |
| Default: | DavQuota Off |
| Context: | server config, virtual host, directory, .htaccess |
| Status: | Extension |
| Module: | mod_dav_fs |
DavQuota sets a quota in bytes for
a given directory as specified by RFC 4331. There are two
special values:
Off Quotas are disabled.None No quota is enforced, but
used and available disk space is reported to
clients that request it.