- try to add a note to explain the behaviour of clients use a pipelined
connection wrt to MaxRequestsPerChild and KeepAlive.
Merge r413683 from trunk:
A little bit more detail, and an example, for how DocumentRoot is
handled. Examples good.
Merge r449032 from trunk:
Capitalization consistency
Submitted by Vincent Bray
Merge r649076 from trunk:
Replace reference to obsolete RFC. Submitted by: Igor Galić.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@655009
13f79535-47bb-0310-9956-
ffa450edef68
<usage>
<p>This directive enables the generation of
<code>Content-MD5</code> headers as defined in RFC1864
- respectively RFC2068.</p>
+ respectively RFC2616.</p>
<p>MD5 is an algorithm for computing a "message digest"
(sometimes called "fingerprint") of arbitrary-length data, with
<p>The <directive>DocumentRoot</directive> should be specified without
a trailing slash.</p>
</usage>
-<seealso><a href="../urlmapping.html">Mapping URLs to Filesystem
-Location</a></seealso>
+<seealso><a href="../urlmapping.html#documentroot">Mapping URLs to Filesystem
+Locations</a></seealso>
</directivesynopsis>
<directivesynopsis>
unless otherwise specified. If the client requests it, chunked
encoding will be used in order to send content of unknown
length over persistent connections.</p>
+
+ <p>When a client uses a Keep-Alive connection it will be counted
+ as a single "request" for the MaxRequestsPerChild directive, regardless
+ of how many requests are sent using the connection.</p>
</usage>
<seealso><directive module="core">MaxKeepAliveRequests</directive></seealso>
<name>LimitRequestFieldSize</name>
<description>Limits the size of the HTTP request header allowed from the
client</description>
-<syntax>LimitRequestFieldsize <var>bytes</var></syntax>
-<default>LimitRequestFieldsize 8190</default>
+<syntax>LimitRequestFieldSize <var>bytes</var></syntax>
+<default>LimitRequestFieldSize 8190</default>
<contextlist><context>server config</context></contextlist>
<usage>
<usage>
<p>Die Direktive aktiviert die Generierung von
- <code>Content-MD5</code>-Headern, wie sie in RFC1864 bzw. RFC2068
+ <code>Content-MD5</code>-Headern, wie sie in RFC1864 bzw. RFC2616
definiert sind.</p>
<p>MD5 ist ein Algorithmus zur Berechnung eines "Datenextrakts"
<status>Experimental</status>
<usage>
- <p>\e$B$3$N%G%#%l%/%F%#%V$O!"\e(BRFC1864 \e$B5Z$S\e(B RFC2068 \e$B$K$*$$$FDj5A$5$l$F$$$k\e(B
+ <p>\e$B$3$N%G%#%l%/%F%#%V$O!"\e(BRFC1864 \e$B5Z$S\e(B RFC2616 \e$B$K$*$$$FDj5A$5$l$F$$$k\e(B
<code>Content-MD5</code> \e$B%X%C%@!<$N@8@.$rM-8z$K$7$^$9!#\e(B</p>
<p>MD5 \e$B$O!"G$0UD9$N%G!<%?$N!V%a%C%;!<%8%@%$%8%'%9%H!W\e(B(\e$B!V;XLf!W\e(B
<name>LimitRequestFieldSize</name>
<description>\e$B%/%i%$%"%s%H$+$i$N\e(B HTTP \e$B%j%/%(%9%H$N%X%C%@$N\e(B
\e$B%5%$%:$r@)8B$9$k\e(B</description>
-<syntax>LimitRequestFieldsize <var>bytes</var></syntax>
-<default>LimitRequestFieldsize 8190</default>
+<syntax>LimitRequestFieldSize <var>bytes</var></syntax>
+<default>LimitRequestFieldSize 8190</default>
<contextlist><context>server config</context></contextlist>
<usage>
make up the basic document tree which will be visible from the
web.</p>
+ <p>For example, if <directive module="core">DocumentRoot</directive>
+ were set to <code>/var/www/html</code> then a request for
+ <code>http://www.example.com/fish/guppies.html</code> would result
+ in the file <code>/var/www/html/fish/guppies.html</code> being
+ served to the requesting client.</p>
+
<p>Apache is also capable of <a href="vhosts/">Virtual
Hosting</a>, where the server receives requests for more than one
host. In this case, a different <directive
be used to dynamically determine the appropriate place from which
to serve content based on the requested IP address or
hostname.</p>
+
+ <p>The <directive module="core">DocumentRoot</directive> directive
+ is set in your main server configuration file
+ (<code>httpd.conf</code>) and, possibly, once per additional <a
+ href="vhosts/">Virtual Host</a> you create.</p>
</section>
<section id="outside"><title>Files Outside the DocumentRoot</title>