You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2002/03/04 21:57:06 UTC
cvs commit: httpd-2.0/docs/manual/mod mod_dav.xml mod_charset_lite.xml
slive 02/03/04 12:57:06
Modified: docs/manual/mod mod_charset_lite.xml
Added: docs/manual/mod mod_dav.xml
Log:
Add mod_dav.xml and cleanup a couple missing things in mod_charset_lite.
Revision Changes Path
1.2 +4 -1 httpd-2.0/docs/manual/mod/mod_charset_lite.xml
Index: mod_charset_lite.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_charset_lite.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -b -u -r1.1 -r1.2
--- mod_charset_lite.xml 4 Mar 2002 20:39:49 -0000 1.1
+++ mod_charset_lite.xml 4 Mar 2002 20:57:06 -0000 1.2
@@ -3,7 +3,7 @@
<modulesynopsis>
<name>mod_charset_lite</name>
-<description>specify character set translation or recoding</description>
+<description>Specify character set translation or recoding</description>
<status>Experimental</status>
<sourcefile>mod_charset_lite.c</sourcefile>
<identifier>charset_lite_module</identifier>
@@ -70,6 +70,7 @@
<directivesynopsis>
<name>CharsetSourceEnc</name>
+<description>Source charset of files</description>
<syntax>CharsetSourceEnc <em>charset</em></syntax>
<contextlist><context>server config</context>
<context>virtual host</context><context>directory</context>
@@ -99,6 +100,7 @@
<directivesynopsis>
<name>CharsetDefault</name>
+<description>Charset to translate into</description>
<syntax>CharsetDefault <em>charset</em></syntax>
<contextlist><context>server config</context>
<context>virtual host</context><context>directory</context>
@@ -127,6 +129,7 @@
<directivesynopsis>
<name>CharsetOptions</name>
+<description>Configures charset tranlation behavior</description>
<syntax>CharsetOptions <em>option</em> [<em>option</em>] ...</syntax>
<default>CharsetOptions <em>DebugLevel=0</em>
<em>NoImplicitAdd</em></default>
1.1 httpd-2.0/docs/manual/mod/mod_dav.xml
Index: mod_dav.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE xml:manual [ <!ENTITY nbsp " "> ]>
<?xml-stylesheet type="text/xsl" href="../style/manual.xsl"?>
<modulesynopsis>
<name>mod_dav</name>
<description>Distributed Authoring and Versioning
(<a href="http://www.webdav.org/">WebDAV</a>) functionality.</description>
<status>Extension</status>
<sourcefile>mod_dav.c</sourcefile>
<identifier>dav_module</identifier>
<summary>
<p>This module provides class 1 and class 2 <a
href="http://www.webdav.org">WebDAV</a> ('Web-based Distributed
Authoring and Versioning') functionality for Apache. This
extension to the HTTP protocol allows creating, moving,
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>
<example>Dav On</example>
<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>
</summary>
<directivesynopsis>
<name>Dav</name>
<description>Enable WebDAV HTTP methods</description>
<syntax>Dav on|off</syntax>
<default>Dav off</default>
<contextlist><context>directory</context></contextlist>
<usage>
<p>Use the <directive>Dav</directive> directive to enable the
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 />
Dav On<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>
<description>Location of the DAV lock database</description>
<name>DavLockDB</name>
<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>
</usage>
</directivesynopsis>
<directivesynopsis>
<name>DavMinTimeout</name>
<description>Minimum amount of time the server holds a lock on
a DAV resource</description>
<syntax>DavMinTimeout <em>seconds</em></syntax>
<default>DavMinTimeout 0</default>
<contextlist><context>directory</context></contextlist>
<usage>
<p>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.</p>
<p>Use the <directive>DavMinTimeout</directive> 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
<directive>DavMinTimeout</directive> can override this to a higher value
(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>
</usage>
</directivesynopsis>
<directivesynopsis>
<name>DavDepthInfinity</name>
<description>Allow PROPFIND, Depth: Infinity requests</description>
<syntax>DavDepthInfinity on|off</syntax>
<default>DavDepthInfinity off</default>
<contextlist><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>
</usage>
</directivesynopsis>
</modulesynopsis>