Running the MVC3 application on the server results in a 403.14 answer

Question

I am trying to get an MVC3 application running in a Windows Server 2008 R2 window. The server runs IIS 7.5. The application is configured with anonymous authentication and an application pool for the v4.0 platform. I granted IUSR and IIS_IUSRS directory access until I switch to using the service account.

I tried the following:

• Registered ASP.NET 4 with IIS (% windir% \ Microsoft.NET \ Framework \ v4.0.30319 \ aspnet_regiis.exe -ir)
• I installed MVC3 on the server from http://www.asp.net/mvc/mvc3 .

I still get HTTP 403.14 response: "HTTP Error 403.14 - Forbidden The web server is configured to not display the contents of this directory."

If I write the dummy index.html file, the page will be served. It seems to me that the module does not intercept the request to indicate the request to the home controller.

The answer . Although MartinHN's answer resolved the issue, it would lead to performance hit when serving static files. Thanks to his answer, I started doing some searches and found that there is an IIS7 patch available that will allow ASP.NET 4 applications to process URLs without continuing without running all the modules for each request. The fix is ​​available here: http://support.microsoft.com/kb/980368 . After installing this hotfix, my application served the content as expected without changing Web.config.

Answer 1

Perhaps this is one of the following ...

Check your web.config for the line:

<system.webServer> <modules runAllManagedModulesForAllRequests="true"> ... </system.webServer> 

And make sure the application pool is installed in Integrated Pipiline.

You can also try resetting handler mappings in IIS. Click on the site → Handler mapping → Go back to the parent (the link should be on the right sidebar).