Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

If classic asp got into a redirect loop, would it be enough to kill the IIS service. Or does the act of redirecting not consume that many resources?

share|improve this question

2 Answers 2

up vote 1 down vote accepted

I believe there is a setting in most browsers that restricts the number of redirects. I believe IE is 7, FireFox is something silly like 20.

I don't entirely agree with Joe. Whilst the act of an unending loop is generally bad, and will eat up resources, your redirect loop involves a connection to a web server, which will clear up once the redirect message is sent to the client. The IIS instance isn't really looping, it's telling your browser to go do something, and it will (should) cleanup after itself.

That being said, if your page does something server intensive, queries databases, holds open other connections, does a bunch of other stuff, then it will cause some issues, but IIS is pretty resilient, and will usually start rejecting connections before crashing. Throw a whole bunch of requests at that page that loops, and you may be looking at memory issues, but entirely depends on what is going on in the script.

share|improve this answer

It would seem to me that if it is in fact a loop that eventually it would cause IIS to crash. A loop has no end, therefore regardless of how little resources each iteration of the loop consumes, eventually all of the resources would be exhausted and IIS would crash.

share|improve this answer
    
Thanks joeqwerty - A very good point, would IIS try to restart itself by default? Or would it stay in the stopped state? Would you get a warning in IIS manager? –  Alex Key Nov 10 '10 at 12:49

Your Answer

 
discard

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.