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

Our loadbalancer looks for "loadbalancer.html"

So today, I deleted the file, but in a browser I could still fetch it.

My eyes crossed, I made sure, 3 ways, that the file was removed from the iis web site home dir. But fetching it gave a nice 200 http response, and the file.

In desperation, I created a new loadbalancer.html, and put some test text in it, and then this new content was retrieved, and then I deleted this file, and THEN it finally gave the 404 as desired.

How can I better understand/control this ?


share|improve this question

In IIS you could set the file to expire immediately. That might help prevent the NLB from caching it.

share|improve this answer
I don't think the nlb was caching it, since when I changed it it changed immediately. (Unless by changing the file IIS handled it differently) – samsmith Jun 15 '12 at 22:32

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.