Apache HTTP Server Version 2.4
|Description:||Provides a comprehensive overview of the server configuration|
mod_info, add the following to your
<Location "/server-info"> SetHandler server-info </Location>
<Location "/server-info"> SetHandler server-info Require host example.com </Location>
Once configured, the server information is obtained by
mod_info is loaded 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.
In particular, this module can leak sensitive information from the configuration directives of other Apache modules such as system paths, usernames/passwords, database names, etc. Therefore, this module should only be used in a controlled environment and always with caution.
You will probably want to use
to limit access to your server configuration information.
<Location "/server-info"> SetHandler server-info # Allow access from server itself Require ip 127.0.0.1 # Additionally, allow access from local workstation Require ip 192.168.1.17 </Location>
By default, the server information includes a list of all enabled modules, and for each module, a description of the directives understood by that module, the hooks implemented by that module, and the relevant directives from the current configuration.
Other views of the configuration information are available by
appending a query to the
server-info request. For
will show all configuration directives.
If the config define
-DDUMP_CONFIG is set,
mod_info will dump the pre-parsed configuration to
stdout during server startup. Pre-parsed means that
evaluated and environment varialbles are replaced. However it does
not represent the final state of the configuration. In particular,
it does not represent the merging or overriding that may happen
for repeated directives.
This is roughly equivalent to the
mod_info provides its information by reading the
parsed configuration, rather than reading the original configuration
file. There are a few limitations as a result of the way the parsed
configuration tree is created:
<IfDefine>are not listed, but the included configuration directives are.
.htaccessfiles are not listed (since they do not form part of the permanent server configuration).
<Directory>are listed normally, but
mod_infocannot figure out the line number for the closing
|Description:||Adds additional information to the module information displayed by the server-info handler|
|Context:||server config, virtual host|
This allows the content of string to be shown as HTML interpreted, Additional Information for the module module-name. Example:
AddModuleInfo mod_deflate.c 'See <a \ href="http://httpd.apache.org/docs/2.4/mod/mod_deflate.html">\ http://httpd.apache.org/docs/2.4/mod/mod_deflate.html</a>'