Httpd mod status: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 17: | Line 17: | ||
=Installation= | =Installation= | ||
Make sure mod_status was either compiled in the binary, or loaded as a dynamic module. | Make sure mod_status was either compiled in the binary (mod_status.c should be in the output of <tt>httpd -l</tt>), or loaded as a dynamic module. | ||
<pre> | <pre> | ||
Line 27: | Line 27: | ||
</pre> | </pre> | ||
If the server acts as a proxy and various URLs are being proxied, insure "/status" is not: | |||
<pre> | |||
ProxyPass /status ! | |||
</pre> | |||
More details [[httpd Location|Location]], [[httpd SetHandler|SetHandler]]. | |||
=Related= | |||
* [[Httpd balancer-manager|balancer-manager]] | |||
Latest revision as of 17:18, 10 January 2017
External
Internal
Overview
mod_status renders a page with information about the server:
- number of workers serving requests and idle.
- status of each worker.
If ExtendedStatus is on, the server maintains and displays extended status information for each request.
Installation
Make sure mod_status was either compiled in the binary (mod_status.c should be in the output of httpd -l), or loaded as a dynamic module.
<Location "/status"> SetHandler server-status </Location> ExtendedStatus On
If the server acts as a proxy and various URLs are being proxied, insure "/status" is not:
ProxyPass /status !
More details Location, SetHandler.