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

This is my mod_proxy config:

<IfModule mod_proxy.c>
<Proxy *>
Order deny,allow
Allow from all

ProxyPass /manage/ http://localhost:9000/manage/
ProxyPassReverse /manage/ http://localhost:9000/manage/

I find that whenever the other website I have on port 9000 doesn't respond correctly, I get sustained 503 errors - that persist even after the website is fixed. In other words, the 503 response seems to be cached.

How can I disable it? I don't think I have enabled caching myself, perhaps this is the default.

share|improve this question
It seems that mod-proxy itself does not do any caching. Did you check your browser cache? – Khaled Jan 16 '12 at 10:18
@Khaled - check out the answer by Shane. – ripper234 Jan 16 '12 at 19:13
possible duplicate of mod_proxy returns 503 errors even after proxied service is back up – ripper234 Mar 19 '12 at 11:28
up vote 9 down vote accepted

mod_proxy marks an unresponsive backend as down when it seems to be down; if no backends are available then it responds with a 503.

By default, a down backend will be marked as such for 60 seconds; until that time passes, it won't retry the connection (and replies with an error message to any connecting clients).

To have it retry immediately, add retry=0 to your ProxyPass directive:

ProxyPass /manage/ http://localhost:9000/manage/ retry=0
share|improve this answer
Awesome, thanks. – ripper234 Jan 16 '12 at 19:12

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.