I just published my website to my local computer(basically copied the folder contents from the Visual Studio 2012 default projects folder to the /inetpub/wwwroot folder). I created a new application pool for my website, added the new application pool identity
to the list of authorized users on the /inetpub/wwwroot/(my website folder).
And it appears the server is responding but with a 200 - OK response with a content-length set to zero as shown in the "Fiddler" view.
I've tried typing the domain alone and I have tried triggering action methods by supplying controller names and action names.
I disabled the "Default Document" module in IIS 7.5. Im not sure if this is part of the problem or not. I am assuming the "Default Document" module has no meaning in an MVC application? Somebody correct me if I am wrong.
I am not sure what else needs to be done to make this work. I am assuming my bindings are correct for the website since the server is sending a 200 OK response but no content.
What might I check to find the problem. This is my first attempt to get an MVC application working on IIS 7.5 on my computer.
Running Windows 7 Ultimate with Service Pack 1 and will continue to do so until hell freezes over or Microsoft releases a proper successor to Windows 7.
Thanks for any help in resolving this matter.
#Edit: I found the problem. I had set the application pool I had created to use .NET Framework Version v2.0 instead of the one my application was targeted for which is v4.0.
Windows 7 Ultimate to the death or until Microsoft comes out of their coma.
I disabled the "Default Document" module and the website appears to be working. It's an MVC application so...it seems to be acceptable but I haven't done much testing at all. I'll see how it goes.
Windows 7 Ultimate to the death or until Microsoft comes out of their coma.
Member
68 Points
592 Posts
Can't get MVC website working under IIS 7.5 - Getting a 200 response from server with content-len...
Sep 01, 2013 08:38 PM|TheNutCracker|LINK
I just published my website to my local computer(basically copied the folder contents from the Visual Studio 2012 default projects folder to the /inetpub/wwwroot folder). I created a new application pool for my website, added the new application pool identity to the list of authorized users on the /inetpub/wwwroot/(my website folder).
And it appears the server is responding but with a 200 - OK response with a content-length set to zero as shown in the "Fiddler" view.
I've tried typing the domain alone and I have tried triggering action methods by supplying controller names and action names.
I disabled the "Default Document" module in IIS 7.5. Im not sure if this is part of the problem or not. I am assuming the "Default Document" module has no meaning in an MVC application? Somebody correct me if I am wrong.
I am not sure what else needs to be done to make this work. I am assuming my bindings are correct for the website since the server is sending a 200 OK response but no content.
What might I check to find the problem. This is my first attempt to get an MVC application working on IIS 7.5 on my computer.
Running Windows 7 Ultimate with Service Pack 1 and will continue to do so until hell freezes over or Microsoft releases a proper successor to Windows 7.
Thanks for any help in resolving this matter.
#Edit: I found the problem. I had set the application pool I had created to use .NET Framework Version v2.0 instead of the one my application was targeted for which is v4.0.
Star
11650 Points
3462 Posts
Re: Can't get MVC website working under IIS 7.5 - Getting a 200 response from server with content...
Sep 02, 2013 01:09 AM|HostingASPNet|LINK
Hello,
You should not disable the default document. You could read more at how to set default page in IIS.
Regards
HowtoASP.NET - Free ASP.NET tutorials with examples and source code.
Member
68 Points
592 Posts
Re: Can't get MVC website working under IIS 7.5 - Getting a 200 response from server with content...
Sep 02, 2013 09:51 AM|TheNutCracker|LINK
I disabled the "Default Document" module and the website appears to be working. It's an MVC application so...it seems to be acceptable but I haven't done much testing at all. I'll see how it goes.