httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rbo...@apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual/mod core.html.en
Date Sat, 10 Nov 2001 13:45:10 GMT
rbowen      01/11/10 05:45:10

  Modified:    htdocs/manual/mod core.html.en
  Log:
  Added more detail, and a compatibility note, for AccessConfig and
  ResourceConfig.
  
  Revision  Changes    Path
  1.202     +31 -11    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.201
  retrieving revision 1.202
  diff -u -r1.201 -r1.202
  --- core.html.en	2001/11/10 03:34:26	1.201
  +++ core.html.en	2001/11/10 13:45:10	1.202
  @@ -259,7 +259,11 @@
       rel="Help"><strong>Context:</strong></a> server config, virtual
       host<br />
        <a href="directive-dict.html#Status"
  -    rel="Help"><strong>Status:</strong></a> core 
  +    rel="Help"><strong>Status:</strong></a> core <br />
  +     <a href="directive-dict.html#Compatibility"
  +    rel="Help"><strong>Compatibility:</strong></a> The ability to
  +    specify a directory, rather than a file name, is only available in
  +    Apache 1.3.13 and later.
   
       <p>The server will read this file for more directives after
       reading the <a href="#resourceconfig">ResourceConfig</a> file.
  @@ -278,12 +282,18 @@
       Historically, this file only contained <a
       href="#directory">&lt;Directory&gt;</a> sections; in fact it
       can now contain any server directive allowed in the <em>server
  -    config</em> context. 
  +    config</em> context. However, since Apache version 1.3.4,
  +    the default <code>access.conf</code> file which ships with 
  +    Apache contains only comments, and all directives are placed
  +    in the main server configuration file, <code>httpd.conf</code>.
   
  -    <p>New in Apache 1.3.13 is the feature that if
  -    <code>AccessConfig</code> points to a directory, rather than a
  +    <p>If <code>AccessConfig</code> points to a directory, rather than
a
       file, Apache will read all files in that directory, and any
  -    subdirectory, and parse those as configuration files.</p>
  +    subdirectory, and parse those as configuration files. Note that
  +    <emph>any</emph> file in the specified directory will be loaded as a
  +    configuration file, so make sure that you don't have stray files in
  +    this directory by mistake, such as temporary files created by your
  +    editor, for example.</p>
   
       <p>See also <a href="#resourceconfig">ResourceConfig</a>.</p>
       <hr />
  @@ -2766,7 +2776,11 @@
       rel="Help"><strong>Context:</strong></a> server config, virtual
       host<br />
        <a href="directive-dict.html#Status"
  -    rel="Help"><strong>Status:</strong></a> core 
  +    rel="Help"><strong>Status:</strong></a> core <br />
  +     <a href="directive-dict.html#Compatibility"
  +    rel="Help"><strong>Compatibility:</strong></a> The ability to
  +    specify a directory, rather than a file name, is only available in
  +    Apache 1.3.13 and later.
   
       <p>The server will read this file for more directives after
       reading the httpd.conf file. <em>File-path</em> is relative to
  @@ -2781,16 +2795,22 @@
       <blockquote>
         <code>ResourceConfig nul</code>
       </blockquote>
  -    Historically, this file contained most directives except for
  +    <p>Historically, this file contained most directives except for
       server configuration directives and <a
       href="#directory">&lt;Directory&gt;</a> sections; in fact it
       can now contain any server directive allowed in the <em>server
  -    config</em> context. 
  +    config</em> context. However, since Apache version 1.3.4, the
  +    default <code>srm.conf</code> file which ships with Apache contains
  +    only comments, and all directives are placed in the main server
  +    configuration file, <code>httpd.conf</code>.</p>
   
  -    <p>New in Apache 1.3.13 is the feature that if
  -    <code>ResourceConfig</code> points to a directory, rather than
  +    <p>If <code>ResourceConfig</code> points to a directory, rather than
       a file, Apache will read all files in that directory, and any
  -    subdirectory, and parse those as configuration files.</p>
  +    subdirectory, and parse those as configuration files. Note that
  +    <emph>any</emph> file in the specified directory will be loaded as a
  +    configuration file, so make sure that you don't have any stray files
  +    in this directory by mistake, such as temporary files created by
  +    your editor, for example.</p>
   
       <p>See also <a href="#accessconfig">AccessConfig</a>.</p>
       <hr />
  
  
  

Mime
View raw message