httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From erikab...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_cache.xml mod_cache.html.en mod_charset_lite.xml mod_charset_lite.html.en mod_mime_magic.xml mod_mime_magic.html.en
Date Sat, 07 Sep 2002 11:55:55 GMT
erikabele    2002/09/07 04:55:55

  Modified:    docs/manual/mod mod_cache.xml mod_cache.html.en
                        mod_charset_lite.xml mod_charset_lite.html.en
                        mod_mime_magic.xml mod_mime_magic.html.en
  Log:
  Some formal changes for better readability plus an example fix
  in mod_charset_lite.xml.
  
  Submitted by: Andre Malo <nd@perlig.de>
  
  Revision  Changes    Path
  1.10      +21 -11    httpd-2.0/docs/manual/mod/mod_cache.xml
  
  Index: mod_cache.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_cache.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- mod_cache.xml	5 Sep 2002 23:15:32 -0000	1.9
  +++ mod_cache.xml	7 Sep 2002 11:55:55 -0000	1.10
  @@ -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>
   
  
  
  
  1.13      +20 -10    httpd-2.0/docs/manual/mod/mod_cache.html.en
  
  Index: mod_cache.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_cache.html.en,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- mod_cache.html.en	6 Sep 2002 23:21:00 -0000	1.12
  +++ mod_cache.html.en	7 Sep 2002 11:55:55 -0000	1.13
  @@ -103,7 +103,7 @@
     CacheEnable  fd    /images <br />
   </code></p></div>
   </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif"
/></a></div><div class="directive-section"><h2><a name="CacheForceCompletion"
id="CacheForceCompletion">CacheForceCompletion</a> <a name="cacheforcecompletion"
id="cacheforcecompletion">Directive</a></h2><table class="directive"><tr><th><a
href="directive-dict.html#Description">Description: 
  -              </a></th><td>Percentage of download to arrive for the cache
to force complete transfert</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
  +              </a></th><td>Percentage of download to arrive for the cache
to force complete transfer</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
                 </a></th><td>CacheForceCompletion <em>Percentage</em></td></tr><tr><th><a
href="directive-dict.html#Default">Default: 
                 </a></th><td><code>CacheForceCompletion 60</code></td></tr><tr><th><a
href="directive-dict.html#Context">Context:
                 </a></th><td>server config</td></tr><tr><th><a
href="directive-dict.html#Status">Status:
  @@ -117,7 +117,7 @@
   <div class="warning">
   This feature is currently <em>not</em> implemented.
   </div>
  - </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif"
/></a></div><div class="directive-section"><h2><a name="CacheIgnoreCacheControl"
id="CacheIgnoreCacheControl">CacheIgnoreCacheControl</a> <a name="cacheignorecachecontrol"
id="cacheignorecachecontrol">Directive</a></h2><table class="directive"><tr><th><a
href="directive-dict.html#Description">Description: 
  +</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif"
/></a></div><div class="directive-section"><h2><a name="CacheIgnoreCacheControl"
id="CacheIgnoreCacheControl">CacheIgnoreCacheControl</a> <a name="cacheignorecachecontrol"
id="cacheignorecachecontrol">Directive</a></h2><table class="directive"><tr><th><a
href="directive-dict.html#Description">Description: 
                 </a></th><td>Ignore requests from the client for uncached
content</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
                 </a></th><td>CacheIgnoreCacheControl</td></tr><tr><th><a
href="directive-dict.html#Context">Context:
                 </a></th><td>server config</td></tr><tr><th><a
href="directive-dict.html#Status">Status:
  @@ -170,13 +170,23 @@
                 </a></th><td>server config</td></tr><tr><th><a
href="directive-dict.html#Status">Status:
                 </a></th><td>Experimental</td></tr><tr><th><a
href="directive-dict.html#Module">Module:
                 </a></th><td>mod_cache</td></tr></table>
  -    <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>
   
  -    <div class="example"><p><code>
  -    # Enable caching of streamed responses up to 64KB:
  -    CacheMaxStreamingBuffer  65536
  -    </code></p></div>
  +<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>
  +
  +<div class="example"><p><code>
  +# Enable caching of streamed responses up to 64KB:<br />
  +CacheMaxStreamingBuffer  65536
  +</code></p></div>
   </div></div><div id="footer"><p class="apache">Maintained by the
<a href="http://httpd.apache.org/docs-project/">Apache HTTP Server Documentation Project</a></p><p
class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a>
| <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a>
| <a href="../sitemap.html">Sitemap</a></p></div></body></html>
  
  
  
  1.5       +3 -3      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.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- mod_charset_lite.xml	23 May 2002 14:50:11 -0000	1.4
  +++ mod_charset_lite.xml	7 Sep 2002 11:55:55 -0000	1.5
  @@ -88,10 +88,10 @@
       APR. Generally, this means that it must be supported by
       iconv.</p>
       
  -<example><title>example</title>
  +<example><title>Example</title>
       &lt;Directory "/export/home/trawick/apacheinst/htdocs/convert"&gt;<br />
       CharsetSourceEnc  UTF-16BE<br />
  -    CharsetDefault    ISO8859-1<br />
  +    CharsetDefault    ISO-8859-1<br />
       &lt;/Directory&gt;
   </example>
       <p>The character set names in this example work with the iconv
  @@ -122,7 +122,7 @@
   <example><title>Example</title>
       &lt;Directory "/export/home/trawick/apacheinst/htdocs/convert"&gt;<br />
       CharsetSourceEnc  UTF-16BE<br />
  -    CharsetDefault    ISO8859-1<br />
  +    CharsetDefault    ISO-8859-1<br />
       &lt;/Directory&gt;
   </example>
   </usage>
  
  
  
  1.10      +3 -3      httpd-2.0/docs/manual/mod/mod_charset_lite.html.en
  
  Index: mod_charset_lite.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_charset_lite.html.en,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- mod_charset_lite.html.en	6 Sep 2002 23:21:00 -0000	1.9
  +++ mod_charset_lite.html.en	7 Sep 2002 11:55:55 -0000	1.10
  @@ -82,7 +82,7 @@
   <div class="example"><h3>Example</h3><p><code>
       &lt;Directory "/export/home/trawick/apacheinst/htdocs/convert"&gt;<br />
       CharsetSourceEnc  UTF-16BE<br />
  -    CharsetDefault    ISO8859-1<br />
  +    CharsetDefault    ISO-8859-1<br />
       &lt;/Directory&gt;
   </code></p></div>
   </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif"
/></a></div><div class="directive-section"><h2><a name="CharsetOptions"
id="CharsetOptions">CharsetOptions</a> <a name="charsetoptions" id="charsetoptions">Directive</a></h2><table
class="directive"><tr><th><a href="directive-dict.html#Description">Description:

  @@ -136,10 +136,10 @@
       APR. Generally, this means that it must be supported by
       iconv.</p>
       
  -<div class="example"><h3>example</h3><p><code>
  +<div class="example"><h3>Example</h3><p><code>
       &lt;Directory "/export/home/trawick/apacheinst/htdocs/convert"&gt;<br />
       CharsetSourceEnc  UTF-16BE<br />
  -    CharsetDefault    ISO8859-1<br />
  +    CharsetDefault    ISO-8859-1<br />
       &lt;/Directory&gt;
   </code></p></div>
       <p>The character set names in this example work with the iconv
  
  
  
  1.4       +6 -6      httpd-2.0/docs/manual/mod/mod_mime_magic.xml
  
  Index: mod_mime_magic.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_mime_magic.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mod_mime_magic.xml	13 Jun 2002 00:02:58 -0000	1.3
  +++ mod_mime_magic.xml	7 Sep 2002 11:55:55 -0000	1.4
  @@ -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>
  
  
  
  1.11      +6 -6      httpd-2.0/docs/manual/mod/mod_mime_magic.html.en
  
  Index: mod_mime_magic.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_mime_magic.html.en,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- mod_mime_magic.html.en	6 Sep 2002 23:21:00 -0000	1.10
  +++ mod_mime_magic.html.en	7 Sep 2002 11:55:55 -0000	1.11
  @@ -31,13 +31,13 @@
       following columns:</p>
   
       <table class="bordered">
  -      <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 />
  @@ -45,7 +45,7 @@
           line</td>
         </tr>
   
  -      <tr valign="top">
  +      <tr>
           <td>2</td>
   
           <td>
  @@ -122,19 +122,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>
  
  
  

Mime
View raw message