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/09/23 23:40:45 UTC

cvs commit: httpd-2.0/docs/manual/mod core.xml core.html.en

slive       2002/09/23 14:40:44

  Modified:    docs/manual/mod core.xml core.html.en
  Log:
  I just spent a few minutes helping someone on the users list figure
  out how to use <IfModule> with php4 and Apache2 (solution
  <IfModule sapi_apache2.c>).  Document the technique for posterity.
  
  Also, try to discourage people from adding random <IfModule>
  sections just for the heck of it.
  
  Revision  Changes    Path
  1.29      +12 -3     httpd-2.0/docs/manual/mod/core.xml
  
  Index: core.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.xml,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -d -b -u -r1.28 -r1.29
  --- core.xml	19 Sep 2002 02:41:15 -0000	1.28
  +++ core.xml	23 Sep 2002 21:40:44 -0000	1.29
  @@ -1036,7 +1036,8 @@
   <usage>
       <p>The <code>&lt;IfModule
       <em>test</em>&gt;...&lt;/IfModule&gt;</code> section is used to
  -    mark directives that are conditional. The directives within an
  +    mark directives that are conditional on the presence of a 
  +    specific module. The directives within an
       <directive type="section">IfModule</directive> section are only
       processed if the <em>test</em> is true. If <em>test</em> is false,
       everything between the start and end markers is ignored.</p>
  @@ -1060,12 +1061,20 @@
       name</em> is <strong>not</strong> included.</p>
   
       <p>The <em>module name</em> argument is the file name of the
  -    module, at the time it was compiled.
  -    For example, <code>mod_rewrite.c</code>.</p>
  +    module, at the time it was compiled.  For example,
  +    <code>mod_rewrite.c</code>.  If a module consists of several
  +    source files, use the name of the file containing the string
  +    <code>STANDARD20_MODULE_STUFF</code>.</p>
   
       <p><directive type="section">IfModule</directive> sections are
       nest-able, which can be used to implement simple multiple-module
       tests.</p>
  +
  +    <note>This section should only be used if you need to have one
  +    configuration file that works whether or not a specific module
  +    is available.  In normal operation, directives need not be
  +    placed in <directive type="section">IfModule</directive>
  +    sections.</note>
   </usage>
   </directivesynopsis>
   
  
  
  
  1.29      +12 -3     httpd-2.0/docs/manual/mod/core.html.en
  
  Index: core.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.html.en,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -d -b -u -r1.28 -r1.29
  --- core.html.en	19 Sep 2002 02:41:14 -0000	1.28
  +++ core.html.en	23 Sep 2002 21:40:44 -0000	1.29
  @@ -842,7 +842,8 @@
                 </a></th><td>core</td></tr></table>
       <p>The <code>&lt;IfModule
       <em>test</em>&gt;...&lt;/IfModule&gt;</code> section is used to
  -    mark directives that are conditional. The directives within an
  +    mark directives that are conditional on the presence of a 
  +    specific module. The directives within an
       <code class="directive">&lt;IfModule&gt;</code> section are only
       processed if the <em>test</em> is true. If <em>test</em> is false,
       everything between the start and end markers is ignored.</p>
  @@ -864,12 +865,20 @@
       name</em> is <strong>not</strong> included.</p>
   
       <p>The <em>module name</em> argument is the file name of the
  -    module, at the time it was compiled.
  -    For example, <code>mod_rewrite.c</code>.</p>
  +    module, at the time it was compiled.  For example,
  +    <code>mod_rewrite.c</code>.  If a module consists of several
  +    source files, use the name of the file containing the string
  +    <code>STANDARD20_MODULE_STUFF</code>.</p>
   
       <p><code class="directive">&lt;IfModule&gt;</code> sections are
       nest-able, which can be used to implement simple multiple-module
       tests.</p>
  +
  +    <div class="note">This section should only be used if you need to have one
  +    configuration file that works whether or not a specific module
  +    is available.  In normal operation, directives need not be
  +    placed in <code class="directive">&lt;IfModule&gt;</code>
  +    sections.</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="Include" id="Include">Include</a> <a name="include" id="include">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description: 
                 </a></th><td>Includes other configuration files from within
   the server configuration files</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax: