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

We have apache servers that proxy content from an application server and also from a legacy web server. We enabled caching using our load balancer, but the caching is not behaving like we expect it to. Here is our setup:

We're setting cache headers specifically for the pages served from our application server using:

<Location ~ /(appDir1|appDir2|appDir3)>
Header set Cache-Control max-age=3600,public

This works fine.

On the legacy server, the sys admin has set this in his Apache virtual host that runs his legacy site:

Header set Cache-Control max-age=0,private,no-cache

However, our load balancers are still caching the legacy content that we proxy.

When we visit http://appHost/legacyDir1 - we see cached content. When we visit http://legacyHost/legacyDir1 - we see the non-cached content. At least in theory, we're expecting to see non-cached at http://appHost/legacyDir1.

Any ideas what we might be missing ... ?


share|improve this question
up vote 0 down vote accepted

The issue was with the load balancer settings. The LB had to be configured to match the various pages that needed to be cached.

share|improve this answer

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.