ok, you may have seen my, and a few other people's, pain staking effort to track down why, intially PUT and then DELETE routing requests in an existing project were not routing. It turns out that it is related to this area of modules and handlers.
From the tests I have done it looks like GET and POST do not need to have the below attribute set.
runAllManagedModulesForAllRequests="true"
However PUT and DELETE will work too when set, and is the default now for a new MVC 3 project.
So the questions I have, is whether it is better to opt in to have every request managed by all modules, for all resources js, css etc.. and exclude them from first from routing, with an .IgnoreRoute, or be more specific about what requests and modules (or
handlers) are used by specifying them in configuration and how would this be done? or is there a better way?
benaw
Member
211 Points
95 Posts
Re: Which http module manages the routing of web api requests?
Mar 06, 2012 04:06 PM|LINK
ok, you may have seen my, and a few other people's, pain staking effort to track down why, intially PUT and then DELETE routing requests in an existing project were not routing. It turns out that it is related to this area of modules and handlers.
From the tests I have done it looks like GET and POST do not need to have the below attribute set.
However PUT and DELETE will work too when set, and is the default now for a new MVC 3 project.
So the questions I have, is whether it is better to opt in to have every request managed by all modules, for all resources js, css etc.. and exclude them from first from routing, with an .IgnoreRoute, or be more specific about what requests and modules (or handlers) are used by specifying them in configuration and how would this be done? or is there a better way?