File this under learning something new every day! Typically method name matching is thought of this way. Looking at the WebAPI source, however, there is a branch of logic for fallback. If the method name doesn’t map (through attribute, or convention) to a supported HTTP verb, then the default is POST. By default action selection … Read more
EDIT This answer relates to Swashbuckle 5.6 and .NET Framework. Please read mwilson’s answer for Swashbuckle and .NET Core You can use the SwaggerOperationAttribute provided by Swashbuckle for that. [SwaggerOperation(“get”)] public IEnumerable<Contact> Get() { …. } [SwaggerOperation(“getById”)] public IEnumerable<Contact> Get(string id) { … } You can use that attribute to add tags and schemes to … Read more
@bet.. I think the genericUriParserOptions is no longer applicable to .net 4.5 or later.. Also as suggested by @JotaBe, you might need to correctly decode the url request. In most case the %2F will be automatically translated to a slash “https://stackoverflow.com/”. So if you need to escape it you will need to decode the ‘%’ … Read more
Web API (1.x-2.x) does not support multiple attribute routes with the same path on different controllers. The result is a 404, because all the route matches more than one controller and at that point Web API will consider the result ambiguous. Note that MVC Core does support this scenario note: MVC Core serves as both … Read more
I was facing the same issue of ‘How to include search parameters as a query string?’, while I was trying to build a web api for my current project. After googling, the following is working fine for me: Api controller action: [HttpGet, Route(“search/{categoryid=categoryid}/{ordercode=ordercode}”)] public Task<IHttpActionResult> GetProducts(string categoryId, string orderCode) { } The url I tried … Read more
From here Routing in Asp.net Mvc 4 and Web Api Darin Dimitrov has posted a very good answer which is working for me. It says… You could have a couple of routes: public static class WebApiConfig { public static void Register(HttpConfiguration config) { config.Routes.MapHttpRoute( name: “ApiById”, routeTemplate: “api/{controller}/{id}”, defaults: new { id = RouteParameter.Optional }, … Read more
Attribute routes cannot be inherited. This was a deliberate design decision. We didn’t feel right and didn’t see valid scenarios where it would make sense to inherit them. Could you give a more realistic scenario as to where you would want to use this? [Update(3/24/2014)] In the upcoming 5.2 release of MVC Web API, there … Read more
By default the route configuration follows RESTFul conventions meaning that it will accept only the Get, Post, Put and Delete action names (look at the route in global.asax => by default it doesn’t allow you to specify any action name => it uses the HTTP verb to dispatch). So when you send a GET request … Read more
I have been scratching my head over this today. My solution is to change the [FromBody] to a HttpRequestMessage, essentially moving up the HTTP stack. In my case I am sending data across the wire which is zipped json which is then base64’d. All this from an android app. The original signature of my web … Read more
Your route map is probably something like this in WebApiConfig.cs: routes.MapHttpRoute( name: “API Default”, routeTemplate: “api/{controller}/{id}”, defaults: new { id = RouteParameter.Optional }); But in order to have multiple actions with the same http method you need to provide webapi with more information via the route like so: routes.MapHttpRoute( name: “API Default”, routeTemplate: “api/{controller}/{action}/{id}”, defaults: … Read more