I'm under the impression that IIS 1.0, 2.0, 3.0 uses a thread pool to handle incoming requests and for low activity the same threads are just reused over and over again. However, if I create a bad ISAPI application that sits in an infinite loop will IIS create more and more threads? #461 - 1997.07.12
Is there a way to override the 404 error in IIS 1.0, 2.0 , or 3.0? I would like to have a page come up listing the web sites on our server when that error happens. #460 - 1997.07.12