Apache mod_status page mangled by mod_rewrite?

Quicktip: if a complicated mod_rewrite setup is making your /server-status inaccessible, just paste the following two lines above all the rewrite rules:

RewriteCond %{REQUEST_URI} /server-status
RewriteRule .* - [L]

and you're ready to set up monitoring of Apache processes.
If the rules are in /etc/apache2, not in .htaccess, you need to reload the web server too:

/etc/init.d/apache2 reload

You know you shouldn't use .htaccess anyway because it hurts performance, right?

Alternatives to mod_rpaf

For years, mod_rpaf has been the standard module for running Apache behind a reverse proxy. Fortunately, it's not the only one and there are alternatives.

• mod_extract_forwarded which is available in EPEL, so it's available for CentOS systems without compling
• mod_remoteip which is built into Apache 2.4 (but good luck finding a production server running 2.4)
• mod_rpaf modified to support X-Forwarded-Proto/X-Forwarded-HTTPS/X-HTTPS