Difference between “MapHttpRoute” and “MapRoute”?
Why using “MapRoute” for “Default” routing, while using “MapHttpRoute” for “DefaultApi” routing?
Why using “MapRoute” for “Default” routing, while using “MapHttpRoute” for “DefaultApi” routing?
Like MVC WebApi runs on the asynchronous ASP.NET pipeline, meaning execution timeout is unsupported.
I’m trying to benchmark (using Apache bench) a couple of ASP.NET Web API 2.0 endpoints. One of which is synchronous and one async.
I’ve done a few searches but haven’t seem to find anything…
I got an error – No action was found on the controller ‘Action’ that matches the request.
Here’s the scenario:
In previous asp.net web api, I implement DefaultHttpControllerSelector to specify how I want the request to locate my controller. I often have different controllers with different names but intended for same processes. The only difference is that one is of higher version than the other.
In WebApiConfig.cs i have the following
I have some class libraries that I use in my ASP.NET Web API app that handle all my backend stuff e.g. CRUD operations to multiple databases like Azure SQL Database, Cosmos DB, etc.
I’m using Web API 2 and I’m getting the following error when I send a POST to my API method using IIS 7.5 on my local box.