rbowen      02/03/25 18:51:19

  Modified:    htdocs/manual/mod core.html.en
  Log:
  Yet more directive examples. Most of these copied over from 2.0 docs.
  
  Revision  Changes    Path
  1.223     +46 -59    httpd-docs-1.3/htdocs/manual/mod/core.html.en
  
  Index: core.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html.en,v
  retrieving revision 1.222
  retrieving revision 1.223
  diff -u -r1.222 -r1.223
  --- core.html.en      23 Mar 2002 03:20:09 -0000      1.222
  +++ core.html.en      26 Mar 2002 02:51:19 -0000      1.223
  @@ -1902,6 +1902,15 @@
       control both standard and nonstandard/unrecognized methods. See
       the documentation for <a href="#limit">&lt;Limit&gt;</a> for
       more details.</p>
  +
  +    <p>For example:</p>
  +
  +    <pre>
  +    &lt;LimitExcept POST GET&gt;
  +    Require valid-user
  +    &lt;/LimitExcept&gt;
  +    </pre>
  +
       <hr />
   
       <h2><a id="limitrequestbody"
  @@ -1945,6 +1954,13 @@
       control over abnormal client request behavior, which may be
       useful for avoiding some forms of denial-of-service
       attacks.</p>
  +
  +    <p>If, for example, you are permitting file upload to a particular
  +    location, and wich to limit the size of the uploaded file to 100K,
  +    you might use the following directive:</p>
  +
  +    <pre>LimitRequestBody 102400</pre>
  +    
       <hr />
   
       <h2><a id="limitrequestfields"
  @@ -1987,6 +2003,11 @@
       The value should be increased if normal clients see an error
       response from the server that indicates too many fields were
       sent in the request.</p>
  +
  +    <p>For example:</p>
  +
  +    <pre>LimitRequestFields 50</pre>
  +
       <hr />
   
       <h2><a id="limitrequestfieldsize"
  @@ -2026,8 +2047,13 @@
   
       <p>This directive gives the server administrator greater
       control over abnormal client request behavior, which may be
  -    useful for avoiding some forms of denial-of-service attacks.
  -    Under normal conditions, the value should not be changed from
  +    useful for avoiding some forms of denial-of-service attacks.</p>
  +
  +    <p>For example:</p>
  +
  +    <pre>LimitRequestFieldSize 16380</pre>
  +
  +    <p>Under normal conditions, the value should not be changed from
       the default.</p>
       <hr />
   
  @@ -2066,8 +2092,13 @@
   
       <p>This directive gives the server administrator greater
       control over abnormal client request behavior, which may be
  -    useful for avoiding some forms of denial-of-service attacks.
  -    Under normal conditions, the value should not be changed from
  +    useful for avoiding some forms of denial-of-service attacks.</p>
  +
  +    <p>For example:</p>
  +
  +    <pre>LimitRequestLine 16380</pre>
  +
  +    <p>Under normal conditions, the value should not be changed from
       the default.</p>
       <hr />
   
  @@ -2335,12 +2366,6 @@
           <th align="LEFT"><strong>Level</strong> </th>
   
           <th align="LEFT"><strong>Description</strong> </th>
  -      </tr>
  -
  -      <tr>
  -        <th>
  -        </th>
  -
           <th align="LEFT"><strong>Example</strong> </th>
         </tr>
   
  @@ -2348,12 +2373,6 @@
           <td><code>emerg</code> </td>
   
           <td>Emergencies - system is unusable.</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
           <td>"Child cannot open lock file. Exiting"</td>
         </tr>
   
  @@ -2361,12 +2380,6 @@
           <td><code>alert</code> </td>
   
           <td>Action must be taken immediately.</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
           <td>"getpwuid: couldn't determine user name from uid"</td>
         </tr>
   
  @@ -2374,25 +2387,13 @@
           <td><code>crit</code> </td>
   
           <td>Critical Conditions.</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
  -        <td>"socket: Failed to get a socket, exiting child"</td>
  +       <td>"socket: Failed to get a socket, exiting child"</td>
         </tr>
   
         <tr>
           <td><code>error</code> </td>
   
           <td>Error conditions.</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
           <td>"Premature end of script headers"</td>
         </tr>
   
  @@ -2400,12 +2401,6 @@
           <td><code>warn</code> </td>
   
           <td>Warning conditions.</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
           <td>"child process 1234 did not exit, sending another
           SIGHUP"</td>
         </tr>
  @@ -2414,12 +2409,6 @@
           <td><code>notice</code> </td>
   
           <td>Normal but significant condition.</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
           <td>"httpd: caught SIGBUS, attempting to dump core in
           ..."</td>
         </tr>
  @@ -2428,12 +2417,6 @@
           <td><code>info</code> </td>
   
           <td>Informational.</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
           <td>"Server seems busy, (you may need to increase
           StartServers, or Min/MaxSpareServers)..."</td>
         </tr>
  @@ -2442,12 +2425,6 @@
           <td><code>debug</code> </td>
   
           <td>Debug-level messages</td>
  -      </tr>
  -
  -      <tr>
  -        <td>
  -        </td>
  -
           <td>"Opening config file ..."</td>
         </tr>
       </table>
  @@ -2460,6 +2437,11 @@
   
       <p>Using a level of at least <code>crit</code> is
       recommended.</p>
  +
  +    <p>For example:</p>
  +
  +    <pre>LogLevel notice</pre>
  +
       <hr />
   
       <h2><a id="maxclients" name="maxclients">MaxClients
  @@ -2513,6 +2495,11 @@
       recommend that this setting be kept to a high value for maximum
       server performance. In Apache 1.1, this is controlled through
       an option to the KeepAlive directive.</p>
  +
  +    <p>For example</p>
  +
  +    <pre>MaxKeepAliveRequests 500</pre>
  +
       <hr />
   
       <h2><a id="maxrequestsperchild"
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to