* Joshua Slive wrote:
> You might also consider resending any other changes that got missed.
> There's been so much going on that a few things obviously slipped
> through the cracks.
ok, checked it. Most of the stuff was committed by Erik. I discovered
just a few things (for now).
mod_cache.xml:
formal changes
mainly inserted some line breaks for reasons of better readability and
maintenance
please note that Erik committed some content changes that were already
on test.perlig.de...
there was some confusion with the directives, here's the diff:
http://cvs.apache.org/viewcvs.cgi/httpd-docs-2.0/manual/mod/mod_cache.xml.diff?r1=1.8&r2=1.9&diff_format=h
mod_charset_lite.xml:
content change: example fix
mod_mime_magic.xml:
just formal changes
nd
--
die (eval q-qq[Just Another Perl Hacker
]
;-)
# Andr� Malo, <http://www.perlig.de/> #
Index: mod_cache.xml
===================================================================
RCS file: /home/cvspublic/httpd-2.0/docs/manual/mod/mod_cache.xml,v
retrieving revision 1.9
diff -u -r1.9 mod_cache.xml
--- mod_cache.xml 5 Sep 2002 23:15:32 -0000 1.9
+++ mod_cache.xml 7 Sep 2002 02:24:56 -0000
@@ -209,7 +209,7 @@
<directivesynopsis>
<name>CacheForceCompletion</name>
-<description>Percentage of download to arrive for the cache to force complete
transfert</description>
+<description>Percentage of download to arrive for the cache to force complete
transfer</description>
<syntax>CacheForceCompletion <em>Percentage</em></syntax>
<default>CacheForceCompletion 60</default>
<contextlist><context>server config</context></contextlist>
@@ -223,8 +223,8 @@
<note type="warning">
This feature is currently <em>not</em> implemented.
</note>
- </usage>
- </directivesynopsis>
+</usage>
+</directivesynopsis>
<directivesynopsis>
<name>CacheMaxStreamingBuffer</name>
@@ -234,15 +234,25 @@
<contextlist><context>server config</context></contextlist>
<usage>
- <p>Maximum number of bytes of a streamed response (i.e., a response where
the entire content is not available all at once, such as a proxy or CGI
response) to buffer before deciding if the response is cacheable. By default,
a streamed response will <em>not</em> be cached unless it has a Content-Length
header. The reason for this is to avoid using a large amount of memory to
buffer a partial response that might end up being too large to fit in the cache
anyway. To enable caching of streamed responses, use CacheMaxStreamingBuffer
to specify the maximum amount of buffer space to use per request.</p>
- <p>Note: Using a nonzero value for CacheMaxStreamingBuffer will not delay
the transmission of the response to the client. As soon as mod_cache copies a
- block of streamed content into a buffer, it sends the block on to the next
- output filter for delivery to the client.</p>
+<p>Maximum number of bytes of a streamed response (i.e., a response where
+the entire content is not available all at once, such as a proxy or CGI
+response) to buffer before deciding if the response is cacheable. By
+default, a streamed response will <em>not</em> be cached unless it has a
+Content-Length header. The reason for this is to avoid using a large amount
+of memory to buffer a partial response that might end up being too large
+to fit in the cache anyway. To enable caching of streamed responses, use
+CacheMaxStreamingBuffer to specify the maximum amount of buffer space to use
+per request.</p>
- <example>
- # Enable caching of streamed responses up to 64KB:
- CacheMaxStreamingBuffer 65536
- </example>
+<p>Note: Using a nonzero value for CacheMaxStreamingBuffer will not delay the
+transmission of the response to the client. As soon as mod_cache copies a
+block of streamed content into a buffer, it sends the block on to the next
+output filter for delivery to the client.</p>
+
+<example>
+# Enable caching of streamed responses up to 64KB:<br />
+CacheMaxStreamingBuffer 65536
+</example>
</usage>
</directivesynopsis>
Index: mod_charset_lite.xml
===================================================================
RCS file: /home/cvspublic/httpd-2.0/docs/manual/mod/mod_charset_lite.xml,v
retrieving revision 1.4
diff -u -r1.4 mod_charset_lite.xml
--- mod_charset_lite.xml 23 May 2002 14:50:11 -0000 1.4
+++ mod_charset_lite.xml 7 Sep 2002 02:24:56 -0000
@@ -88,10 +88,10 @@
APR. Generally, this means that it must be supported by
iconv.</p>
-<example><title>example</title>
+<example><title>Example</title>
<Directory "/export/home/trawick/apacheinst/htdocs/convert"><br />
CharsetSourceEnc UTF-16BE<br />
- CharsetDefault ISO8859-1<br />
+ CharsetDefault ISO-8859-1<br />
</Directory>
</example>
<p>The character set names in this example work with the iconv
@@ -122,7 +122,7 @@
<example><title>Example</title>
<Directory "/export/home/trawick/apacheinst/htdocs/convert"><br />
CharsetSourceEnc UTF-16BE<br />
- CharsetDefault ISO8859-1<br />
+ CharsetDefault ISO-8859-1<br />
</Directory>
</example>
</usage>
Index: mod_mime_magic.xml
===================================================================
RCS file: /home/cvspublic/httpd-2.0/docs/manual/mod/mod_mime_magic.xml,v
retrieving revision 1.3
diff -u -r1.3 mod_mime_magic.xml
--- mod_mime_magic.xml 13 Jun 2002 00:02:58 -0000 1.3
+++ mod_mime_magic.xml 7 Sep 2002 02:24:58 -0000
@@ -35,13 +35,13 @@
following columns:</p>
<table border="1">
- <tr valign="top">
+ <tr>
<th>Column</th>
<th>Description</th>
</tr>
- <tr valign="top">
+ <tr>
<td>1</td>
<td>byte number to begin checking from<br />
@@ -49,7 +49,7 @@
line</td>
</tr>
- <tr valign="top">
+ <tr>
<td>2</td>
<td>
@@ -126,19 +126,19 @@
</td>
</tr>
- <tr valign="top">
+ <tr>
<td>3</td>
<td>contents of data to match</td>
</tr>
- <tr valign="top">
+ <tr>
<td>4</td>
<td>MIME type if matched</td>
</tr>
- <tr valign="top">
+ <tr>
<td>5</td>
<td>MIME encoding if matched (optional)</td>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
