Module mod_dav

The Dav directive enables the WebDAV HTTP methods for the given container. You may want to add a <Limit> clause inside the location directive to limit access to Dav-enabled locations.

Parameter: on | off | [provider name]

• When on is specified, WebDAV HTTP methods are enabled for the given container, using the default provider "filesystem".
• When off is specified, WebDAV HTTP methods are disabled for the given container.
• The optional provider name parameter is used to specify the Dav provider for a directory or location. There are no Server restrictions on the number or types of characters in the provider name. The provider name used on the Dav directive is case sensitive.

The values on and off are not case sensitive.

Example 1:

DavLockDB /tmp/DavLock
LoadModule dav_module /qsys.lib/qhttpsvr.lib/qzsrdav.srvpgm 
LoadModule dav_fs_module /qsys.lib/qhttpsvr.lib/qzsrdavf.srvpgm 
<Location /foo>
   Dav on
</Location>

Example 2:

DavQsysLockDB mylib/DavLock
LoadModule dav_module /qsys.lib/qhttpsvr.lib/qzsrdav.srvpgm 
LoadModule dav_qsys_module /qsys.lib/qhttpsvr.lib/qzsrdavqs.srvpgm 

<Directory /qsys.lib/webserver.lib*>
   Dav qsys
</Directory>

If you specify "Dav on" in a directory, you will get the default provider "filesystem".

The Dav directive does not override like other directory-scoped directives. You cannot turn Dav on in one directory, and then turn it off in a sub-directory. You also cannot change providers in a sub-directory. You will receive runtime errors if this happens. The following examples are invalid and will cause the HTTP Server to generate a runtime error:

<Directory />
   AllowOverride None
   Order Deny,Allow
   Deny From all
   Dav filesystem
   </Files>
      Dav off
   </Files>
</Directory>

Another invalid example:

<Directory /www/parentDirectory>
   Dav filesystem
<Directory>
<Directory /www/parentDirectory/childDirectory>
   Dav off
</Directory>

The DavDepthInfinity directive allows 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.

Parameter: on | off

• When on is specified, processing of PROPFIND requests containing the header 'Depth: Infinity' is allowed.
• When off is specified, processing of PROPFIND requests containing the header 'Depth: Infinity' is not allowed.

The DavLockDB directive specifies 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.

Parameter: filename

• The filename parameter specifies the full path to the lock database, excluding an extension.

This directive is required if you are using Dav with the default (filesystem) provider. For example,

DavLockDB /tmp/DavLock

The DavMinTimeout directive specifies, in seconds, the minimum lock timeout to return to a client. Microsoft Web Folders defaults to a timeout of 120 seconds; the DavMinTimeout can override this to a higher value (like 600 seconds) to reduce the chance of the client losing the lock due to network latency.

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. The maximum value for minutes is 166; the maximum value for seconds is 9999.

Parameter: seconds

• The seconds parameter is any integer value from 0 to 9999.

The DAVQsysLockDB directive specifies the library qualified database file that the QSYS repository manager uses to track user locks of QSYS resources. The library must exist. The names of the library and file must follow the QSYS file system naming rules.

Parameter: library/filename

• The library/filename parameter specifies the library qualified database file that the QSYS repository manager uses to track user locks of QSYS resources.