What are managed modules?

I recently pushed some ASP.NET MVC 3 and 4 to IIS 7 and had serious problems. A typical fix is ​​to include the following in Web.Config:

<system.webServer> <httpErrors errorMode="Detailed" /> <asp scriptErrorSentToBrowser="true"/> <modules runAllManagedModulesForAllRequests="true" /> </system.webServer> 

My question is why? What is a managed module and how do they work with ASP.NET MVC / C #?

EDIT: After further testing, I found that this problem does not exist on Server 2008 R2 and IIS 7.5, but the question is still what is a managed module and how do I know if I use it in my code?

+6
source share
1 answer

A module is an ASP.Net component that connects to a point in the query pipeline; There are many β€œofficial” modules, although you can also copy your own .

IIS listing of modules

As you can see, the modules perform many functions, including output caching, various types of authorization and authentication, and much more.


It’s best not to run all managed modules ; instead, if possible, find out which modules are needed for a particular application or platform. For ASP.Net MVC, this is most likely the routing module: System.Web.Routing.UrlRoutingModule .

+5
source

All Articles