You are looking at the documentation for the 1.3 version of the Apache HTTP Server, which is no longer maintained, and has been declared "end of life". If you are in fact still using the 1.3 version, please consider upgrading. The current version of the server is 2.4.
This module provides information on server activity and performance.
Source File: mod_status.c
Module Identifier: status_module
Compatibility: Available in Apache 1.1 and later.
The Status module allows a server administrator to find out how well their server is performing. A HTML page is presented that gives the current server statistics in an easily readable form. If required this page can be made to automatically refresh (given a compatible browser). Another page gives a simple machine-readable list of the current server state.
The details given are:
Details marked "(*)" are only available with
<Location /server-status> SetHandler server-status Order Deny,Allow Deny from all Allow from .foo.com </Location>
You can now access server statistics by using a Web browser
to access the page
Alternatively, if you have
lynx installed, you can
also get a server statics report from the command line by running
apachectl status, or, for the extended
apachectl fullstatus. See the apachectl documentation for
Note that mod_status will only work when you are running Apache in standalone mode and not inetd mode.
http://your.server.name/server-status?refresh=Nto refresh the page every N seconds.
http://your.server.name/server-status?auto. This is useful when automatically run, see the Perl program in the
/supportdirectory of Apache,
It should be noted that if mod_status is compiled into the server, its handler capability is available in all configuration files, including per-directory files (e.g., .htaccess). This may have security-related ramifications for your site.
This directive controls whether the server keeps track of extended status information for each request. This is only useful if the status module is enabled on the server.
This setting applies to the entire server, and cannot be enabled or disabled on a virtualhost-by-virtualhost basis.