ASP.NET gone FUBAR on a production machine
<p>Today we tried to put an ASP.NET application I helped to develop on yet another production machine. But this time we got a very weird error.</p>

<p>First of all, from all the ASP.NET pages, only Login.aspx was working. The rest just show a blank screen when they should have redirected to Login.aspx. The HTTP response is 200, but no content.</p>

<p>Even worse - when I try to enter the address of some inexistent ASPX page, I also get HTTP 200! Or, when I enter gibberish in some existing ASPX page code (which should have been accessible without login) I also get HTTP 200.</p>

<p>If I enter the name of some inexistent resource (like asdasd.jpg), I get the expected 404.</p>

<p>The redirect to login page is written manually in Global.asax. That's because the application has to use some alternate methods of authentication as well, so I can't just use Forms Authentication. I would suspect that Global.asax is failing, if not for the working Login page.</p>

<p>Noteworthy facts are also that this machine is both a Domain Controller and has SharePoint installed on it. Although the website in question is listed in SharePoint's exception list.</p>
