Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got some webhealth checks that mainly see if the server is still alive. At the moment when each get is performed it spins up an instance of the web app on the server. I'd like to just have apache2.4 rely with a 200 for the specific IP addresses that are used to run the health check.

Is that possible? How do you configure Apache to return a 200 (without doing anything else) when the GET comes from a specific set of IP addresses?


To clarify why the question has been asked. The particular monitoring I'm concerned about is simple the monitoring of whether the server is up or down. The more detailed monitoring is managed by other methods and wouldn't be set to return 200.

The reason is that each web health check get (and there are multiple from around the world all at the same time) starts up the application stack and so produces an associated overhead. I want to avoid that overhead for what is simply a "are you alive" test.

share|improve this question
What are you trying to check the health of? Apache the app or something else ? – Iain Nov 30 '13 at 16:34
Just whether the server is operational. Not necessarily whether the app is running. I've got other monitoring for that. – Simon Cast Dec 2 '13 at 11:21

Sure, that's possible. But that completely defeats the purpose of checking the health of the service...

RewriteCond %{REMOTE_HOST}
RewriteRule . /path/to/some/static/file.html
share|improve this answer
Ok thanks. I'll look into that. This particular check is whether the server is up or down as opposed to whether the app itself is working. – Simon Cast Dec 2 '13 at 11:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.