Hard to describe, but this is what is being served by IIS with an ASP.NET 4.0 MVC 2.0 setup. Does anybody have any idea as to why this is happening? It is happening locally for me as well as our staging environment on another server (making me think it’s code based…). Let me know what other information would be helpful.
Cheers
Testing a bad ViewData element was causing the freak out. Still strange that it decided to do that instead of return an error message though…
Check more discussion of this question.