marc 97/02/26 18:56:33
Modified: htdocs/manual/mod mod_info.html mod_status.html
Log:
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
Revision Changes Path
1.3 +32 -6 apache/htdocs/manual/mod/mod_info.html
Index: mod_info.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_info.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** mod_info.html 1996/11/21 10:30:48 1.2
--- mod_info.html 1997/02/27 02:56:32 1.3
***************
*** 9,16 ****
<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
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:
--- 9,17 ----
<h1>Module mod_info</h1>
This module is contained in the <code>mod_info.c</code> file. It
! 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,40 ****
</Location>
</PRE>
! You may wish to add a limit clause inside the location 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>
!
<!--#include virtual="footer.html" -->
</BODY>
</HTML>
-
--- 30,66 ----
</Location>
</PRE>
! You may wish to add a
! <A
! HREF="core.html#limit"
! ><Limit></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>
1.4 +9 -1 apache/htdocs/manual/mod/mod_status.html
Index: mod_status.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_status.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C3 -r1.3 -r1.4
*** mod_status.html 1997/02/03 01:18:17 1.3
--- mod_status.html 1997/02/27 02:56:32 1.4
***************
*** 80,86 ****
AUX_CFLAGS= (something) -DSTATUS
</pre>
<!--#include virtual="footer.html" -->
</BODY>
</HTML>
-
--- 80,94 ----
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>
