* Andr� Malo wrote:
[mod_dav split]
ok, since I'm currently sitting on typing some content, I've tried to
extend the dav docs, too. you'll find a new patch and a new mod_dav_fs.xml
attached for yet another review.
nd
--
sub the($){+shift} sub answer (){ord q
[* It is always 42! *] }
print the answer
# Andr� Malo # http://www.perlig.de/ #
? manual/build
? manual/mod/mod_dav_fs.html.en
? manual/mod/mod_dav_fs.xml
Index: manual/sitemap.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/sitemap.xml,v
retrieving revision 1.9
diff -u -r1.9 sitemap.xml
--- manual/sitemap.xml 5 Nov 2002 18:09:07 -0000 1.9
+++ manual/sitemap.xml 12 Nov 2002 03:13:17 -0000
@@ -144,6 +144,7 @@
<modulefile>mod_cgid.xml</modulefile>
<modulefile>mod_charset_lite.xml</modulefile>
<modulefile>mod_dav.xml</modulefile>
+ <modulefile>mod_dav_fs.xml</modulefile>
<modulefile>mod_deflate.xml</modulefile>
<modulefile>mod_dir.xml</modulefile>
<modulefile>mod_echo.xml</modulefile>
Index: manual/mod/mod_dav.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_dav.xml,v
retrieving revision 1.4
diff -u -r1.4 mod_dav.xml
--- manual/mod/mod_dav.xml 23 May 2002 14:50:11 -0000 1.4
+++ manual/mod/mod_dav.xml 12 Nov 2002 03:13:19 -0000
@@ -18,26 +18,36 @@
copying, and deleting resources and collections on a remote web
server.</p>
- <p>To enable mod_dav, add the following to a container in your
- <code>httpd.conf</code> file:</p>
+ <p>To enable <module>mod_dav</module>, add the following to a
+ container in your <code>httpd.conf</code> file:</p>
-<example>Dav On</example>
+ <example>Dav On</example>
+ <p>The example above activates the DAV file system provider. This
+ provider is implemented by the <module>mod_dav_fs</module> module.
+ Therefore this module has to be compiled into the server or has to
+ be loaded at runtime using the <directive module="mod_so"
+ >LoadModule</directive> directive.</p>
+
<p>Also, specify a valid filename for the DAV lock database by
adding the following to the global section in your
<code>httpd.conf</code> file:</p>
-<example>DavLockDB /tmp/DavLock
- <em>(Any web-server writable filename, without an
- extension)</em>
-</example>
+ <example>
+ DavLockDB /tmp/DavLock<br />
+ # (Any web-server writable filename,<br />
+ # without an extension)<br />
+ </example>
</summary>
+<seealso><directive module="mod_dav_fs">DavLockDB</directive></seealso>
+<seealso><directive module="core">LimitXMLRequestBody</directive></seealso>
+<seealso><a href="http://www.webdav.org";>WebDAV Resources</a></seealso>
<directivesynopsis>
<name>Dav</name>
<description>Enable WebDAV HTTP methods</description>
-<syntax>Dav on|off</syntax>
-<default>Dav off</default>
+<syntax>Dav On|Off|<var>provider-name</var></syntax>
+<default>Dav Off</default>
<contextlist><context>directory</context></contextlist>
<usage>
@@ -45,45 +55,46 @@
WebDAV HTTP methods for the given container. You may wish to add a
<directive module="core" type="section">Limit</directive> clause
inside the <directive module="core"
- type="section">location</directive> directive to limit access to
- DAV-enabled locations.</p>
-
-<example><title>Example</title>
- DavLockDB /tmp/DavLock<br />
- <br />
- <Location /foo><br />
+ type="section">Location</directive> directive to limit access to
+ DAV-enabled locations. If you want to set the maximum amount of
+ bytes that a DAV client can send at one request, you have to use
+ the <directive module="core">LimitXMLRequestBody</directive>
+ directive. The "normal" <directive module="core"
+ >LimitRequestBody</directive> directive has no effect on DAV requests!</p>
+
+ <example><title>Example</title>
+ DavLockDB /tmp/DavLock<br />
+ <br />
+ <Location /foo><br />
+ <indent>
Dav On<br />
- <br />
+ <br />
AuthType Basic<br />
AuthName DAV<br />
AuthUserFile user.passwd<br />
- <br />
- <LimitExcept GET HEAD OPTIONS><br />
- require user admin<br />
- </LimitExcept><br />
- </Location><br />
-</example>
-</usage>
-</directivesynopsis>
-
-<directivesynopsis>
-<name>DavLockDB</name>
-<description>Location of the DAV lock database</description>
-<syntax>DavLockDB <em>file-path</em></syntax>
-<contextlist><context>server config</context><context>virtual host</context>
-</contextlist>
-
-<usage>
- <p>Use the <directive>DavLockDB</directive> 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. The utility
- <code>modules/dav/util/lockview</code> can be used from the server
- to display all locks in a lock database.</p>
-
-<example><title>Example</title>
-DavLockDB /tmp/DavLock
-</example>
+ <br />
+ <LimitExcept GET HEAD OPTIONS><br />
+ <indent>
+ require user admin<br />
+ </indent>
+ </LimitExcept><br />
+ </indent>
+ </Location><br />
+ </example>
+
+ <p>The value <code>On</code> is actually an alias for the default
+ provider <code>filesystem</code> which is served by the <module
+ >mod_dav_fs</module> module. Note, that once you have DAV enabled
+ for some location, it <em>cannot</em> be disabled for sublocations.</p>
+
+ <note type="warning"><title>Security</title>
+ <p>The use of HTTP Basic Authentication is not recommended. You
+ should use at least HTTP Digest Authentication, which is provided by
+ the <module>mod_auth_digest</module> module. Nearly all WebDAV clients
+ support this authentication method. Of course, if you want to be
+ really secure, you should use the service of <module
+ >mod_ssl</module>.</p>
+ </note>
</usage>
</directivesynopsis>
@@ -91,9 +102,10 @@
<name>DavMinTimeout</name>
<description>Minimum amount of time the server holds a lock on
a DAV resource</description>
-<syntax>DavMinTimeout <em>seconds</em></syntax>
+<syntax>DavMinTimeout <var>seconds</var></syntax>
<default>DavMinTimeout 0</default>
-<contextlist><context>directory</context></contextlist>
+<contextlist><context>server config</context><context>virtual host</context>
+<context>directory</context></contextlist>
<usage>
<p>When a client requests a DAV resource lock, it can also
@@ -108,11 +120,13 @@
(like 600 seconds) to reduce the chance of the client losing
the lock due to network latency.</p>
-<example><title>Example</title>
- <Location /MSWord><br />
- DavMinTimeout 600<br />
- </Location><br />
-</example>
+ <example><title>Example</title>
+ <Location /MSWord><br />
+ <indent>
+ DavMinTimeout 600<br />
+ </indent>
+ </Location>
+ </example>
</usage>
</directivesynopsis>
@@ -121,13 +135,14 @@
<description>Allow PROPFIND, Depth: Infinity requests</description>
<syntax>DavDepthInfinity on|off</syntax>
<default>DavDepthInfinity off</default>
-<contextlist><context>directory</context></contextlist>
+<contextlist><context>server config</context><context>virtual host</context>
+<context>directory</context></contextlist>
<usage>
<p>Use the <directive>DavDepthInfinity</directive> 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.</p>
+ allow the processing of <code>PROPFIND</code> requests containing the
+ header 'Depth: Infinity'. Because this type of request could constitute
+ a denial-of-service attack, by default it is not allowed.</p>
</usage>
</directivesynopsis>
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
<modulesynopsis>
<name>mod_dav_fs</name>
<description>filesystem provider for <module>mod_dav</module></description>
<status>Extension</status>
<sourcefile>mod_dav_fs.c</sourcefile>
<identifier>dav_fs_module</identifier>
<summary>
<p>This module <em>requires</em> the service of <module
>mod_dav</module>. It acts as a support module for <module
>mod_dav</module> and provides access to resources located in the
server's file system. The formal name of this provider is
<code>filesystem</code>. Since <code>filesystem</code> is the default
provider for <module>mod_dav</module>, you may specify:</p>
<example>
# either<br />
Dav On<br />
<br />
# or<br />
Dav filesystem
</example>
</summary>
<seealso><module>mod_dav</module></seealso>
<directivesynopsis>
<name>DavLockDB</name>
<description>Location of the DAV lock database</description>
<syntax>DavLockDB <var>file-path</var></syntax>
<contextlist><context>server config</context><context>virtual host</context>
</contextlist>
<usage>
<p>Use the <directive>DavLockDB</directive> 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 <directive
module="core">ServerRoot</directive>. The implementation of
<module>mod_dav_fs</module> uses a SDBM database to track user
locks.</p>
<!-- XXX: someone should add that tool to the support directory...
The utility <code>modules/dav/util/lockview</code> can be used from
the server to display all locks in a lock database.</p> -->
<example><title>Example</title>
DavLockDB logs/DavLock
</example>
</usage>
</directivesynopsis>
</modulesynopsis>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
