Clarify that mod_info uses startup-config and not running-config

and note that mod_info and mod_status can be enabled from things
like .htaccess files.

Submitted by:	Ken Coar

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77688 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_info.html b/docs/manual/mod/mod_info.html
index fa9862908726198abe5ac6d8f070253ef923b251..34f7ea0a98e752de0595048d96d9aae10d69237d 100644 (file)
--- a/docs/manual/mod/mod_info.html
+++ b/docs/manual/mod/mod_info.html
@@ -9,8 +9,9 @@
 <h1>Module mod_info</h1>
 
 This module is contained in the <code>mod_info.c</code> file.  It
-provides a comprehensive overview of the current server configuration
-including all installed modules.  This module is not compiled into the
+provides a comprehensive overview of the server configuration
+including all installed modules and directives in the configuration
+files.  This module is not compiled into the
 server by default.  It is only available in Apache 1.1 and later. To
 enable it, add the following line to the server build Configuration
 file, and rebuild the server:
@@ -29,12 +30,37 @@ SetHandler server-info
 &lt;/Location&gt;
 </PRE>
 
-You may wish to add a limit clause inside the location directive to limit
-access to your server configuration information.<p>
+You may wish to add a
+<A
+ HREF="core.html#limit"
+>&lt;Limit&gt;</A>
+clause inside the
+<A
+ HREF="core.html#location"
+>location</A>
+directive to limit access to your server configuration information.<p>
 Once configured, the server information is obtained by accessing
 <tt>http://your.host.dom/server-info</tt><p>
-
+<BLOCKQUOTE>
+ <STRONG>
+  Note that the configuration files are read by the module at run-time,
+  and therefore the display may <EM>not</EM> reflect the running
+  server's active configuration if the files have been changed since the
+  server was last reloaded.  Also, the configuration files must be
+  readable by the user as which the server is running (see the
+  <A
+   HREF="core.html#user"
+  ><SAMP>User</SAMP></A>
+  directive), or else the directive settings will not be listed.
+  <P>
+  It should also be noted that if <SAMP>mod_info</SAMP> is compiled into
+  the server, its handler capability is available in <EM>all</EM>
+  configuration files, including <EM>per</EM>-directory files
+  (<EM>e.g.</EM>, <SAMP>.htaccess</SAMP>).  This may have
+  security-related ramifications for your site.
+  </P>
+ </STRONG>
+</BLOCKQUOTE>
 <!--#include virtual="footer.html" -->
 </BODY>
 </HTML>
-

diff --git a/docs/manual/mod/mod_status.html b/docs/manual/mod/mod_status.html
index 1ce412c99da6a0febe62376131ae2814da39119a..79fd69e01b39a16879d429475d723c1d2914dfc3 100644 (file)
--- a/docs/manual/mod/mod_status.html
+++ b/docs/manual/mod/mod_status.html
@@ -80,7 +80,15 @@ Do this by adding the following to the AUX_CFLAGS line in the
        AUX_CFLAGS= (something) -DSTATUS
 </pre>
 
+<BLOCKQUOTE>
+ <STRONG>
+  It should be noted that if <SAMP>mod_status</SAMP> is compiled into
+  the server, its handler capability is available in <EM>all</EM>
+  configuration files, including <EM>per</EM>-directory files
+  (<EM>e.g.</EM>, <SAMP>.htaccess</SAMP>).  This may have
+  security-related ramifications for your site.
+ </STRONG>
+</BLOCKQUOTE>
 <!--#include virtual="footer.html" -->
 </BODY>
 </HTML>
-