Quantcast
Viewing all articles
Browse latest Browse all 27852

IIS7 with multiple sites is serving 404 for stopped site

 Hi all!

We have multiple sites on our IIS7, each with an individual IP bound on the machine. For all sites we have 4 IPs in the bindings, of which only one per site is of current machine. The other 3 IPs per site are for the other 3 machines (we have same ApplicationHost.config for all 4 machines).

Now we have a Loadbalancer distributing requests from outside to this 4 machines. The LB is set up to detect if a site is not responding. If on a site there is a 404 the LB doesn't react, since the user typed a wrong path and shout get a 404.

The problem we encounter: IIS7 serves a 404 if I stop a particular site in it and navigate to it. LB seems to get similar: It does not detect the site as "failed" if it is stopped. This is because the IIS answers a request to a stopped site with a 404. I only get a "connection problem" if I stop all sites on the IIS. By then, the LB also detects the site as failed. If I have only one site on the IIS and stop the site, I get the expected "connection problem". This behaviour was different on IIS6, our loadbalancing infrastructure worked correctly before migrating to IIS7.

Is there any explanation to that?


Viewing all articles
Browse latest Browse all 27852

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>