ASP.NET Web API controller with attribute routing doesn't work without a route name

Question

I use attribute routing, but when I specify an empty Route attribute I get the following error:

405.0 - Method Not Allowed

However, if I add a route name in the attribute, like [Route("bar")], everything works as expected.

Why would one of these action methods work as expected, while the other one yields a 405 error?

[System.Web.Http.RoutePrefix("foo")]
public partial class MyController : ApiController
{
   [System.Web.Http.HttpPost]
   [System.Web.Http.Route("bar")] // I am able to POST to /foo/bar
   public async Task<MyResponseModel> BarMethod([FromBody]MyArgumentsModel arguments)
   {

   }

   [System.Web.Http.HttpPost]
   [System.Web.Http.Route] // Error when I POST to /foo, "Method Not Allowed"
   public async Task<MyResponseModel> FooMethod([FromBody]MyArgumentsModel arguments)
   {

   }
}

Any ideas what I could be missing?

You don't need to use [System.Web.Http.Route]. Just remove it and the method will inherit the controllers route. — Marcus Höglund
– Marcus Höglund, Commented Sep 20, 2016 at 10:52

Nkosi · Accepted Answer · 2016-09-20 10:53:56Z

2

You need to include an empty string to the route attribute [Route("")] in order for it to work as the default route when using the route prefix.

The following article shows how it is done

Source: Attribute Routing in ASP.NET Web API 2

The result of the suggested change would look like this

[RoutePrefix("foo")]
public partial class MyController : ApiController {
   //eg POST foo/bar
   [HttpPost]
   [Route("bar")]
   public async Task<MyResponseModel> BarMethod([FromBody]MyArgumentsModel arguments) {
      //...
   }

   //eg POST foo    
   [HttpPost]
   [Route("")]
   public async Task<MyResponseModel> FooMethod([FromBody]MyArgumentsModel arguments) {
       //...
   }
}

edited Sep 20, 2016 at 10:53

answered Sep 20, 2016 at 10:34

Nkosi

249k38 gold badges472 silver badges506 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Ted Nyberg Over a year ago

Thanks for your help! However, adding an empty string yields the same result. :/

Nkosi Over a year ago

Check the examples in the article liked in the answer.

giammin · Accepted Answer · 2016-09-20 10:45:43Z

1

Attribute routing can be combined with convention-based routing. To define convention-based routes, call the MapHttpRoute method.

public static class WebApiConfig
{
    public static void Register(HttpConfiguration config)
    {
        // Attribute routing.
        config.MapHttpAttributeRoutes();

        // Convention-based routing.
        config.Routes.MapHttpRoute(name:"DefaultApi", 
            routeTemplate: "api/{controller}/{id}",
            defaults: new { id = RouteParameter.Optional } );
    }
}

edited Sep 20, 2016 at 10:45

answered Sep 20, 2016 at 10:32

giammin

19.1k9 gold badges74 silver badges90 bronze badges

6 Comments

Ted Nyberg Over a year ago

Thanks for helping! Although I already have that exact configuration in place. :)

giammin Over a year ago

@TedNyberg Then try to rename FooMethod to Post

Ted Nyberg Over a year ago

I tried that before, but it made no difference. :/ Thanks though!

giammin Over a year ago

@TedNyberg i have an application online that currently works with this configuration/ attributes... what version of webapi/ framework are you using?

Ted Nyberg Over a year ago

Version 5.2.3. Weird thing is, this has worked before. :/

|

Collectives™ on Stack Overflow

ASP.NET Web API controller with attribute routing doesn't work without a route name

2 Answers 2

2 Comments

6 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

6 Comments

Your Answer

Sign up or log in

Post as a guest

Related