Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Mar 06, 2012 04:06 PM by benaw
Mar 06, 2012 11:38 AM|LINK
Mar 06, 2012 12:09 PM|LINK
check this link, are you talking about this? Please let me know did it helped you?
Mar 06, 2012 12:13 PM|LINK
I don't see a reference to the asp.net module which manages the requests.
Mar 06, 2012 12:15 PM|LINK
That would be System.Web.Routing.UrlRoutingModule, unless the Web API guys are hooking into the routing engine some other way.
Mar 06, 2012 12:24 PM|LINK
It would be helpful to know for sure.
Mar 06, 2012 03:20 PM|LINK
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?