CODEWITHSUNDEEP
c#asp.netasp.net-mvcasp.net-web-apiasp.net-web-api-routing
john doe
john doe

Reputation: 9700

ASP.NET Web API Route Controller Not Found

I am trying to post to the following Web API: 

http://localhost:8543/api/login/authenticate

LoginApi (Web API) is defined below: 

[RoutePrefix("login")]
public class LoginApi : ApiController
{
    [HttpPost]
    [Route("authenticate")]
    public string Authenticate(LoginViewModel loginViewModel)
    {  
        return "Hello World"; 
    }
}

WebApiConfig.cs: 

public static void Register(HttpConfiguration config)
{
    // Web API configuration and services

    // Web API routes
    config.MapHttpAttributeRoutes();

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

Here is the error I get: 

Request URL:http://localhost:8543/api/login/authenticate
Request Method:POST
Status Code:404 Not Found
Remote Address:[::1]:8543

Upvotes: 3

Views: 14250

Answers (3)

Nkosi
Nkosi

Reputation: 247611

You are using login as your route prefix on your controller so trying to call 

http://localhost:8543/api/login/authenticate

will not be found as this code

[RoutePrefix("login")]
public class LoginApi : ApiController
{
    //eg:POST login/authenticate.
    [HttpPost]
    [Route("authenticate")]
    public string Authenticate(LoginViewModel loginViewModel)
    {  
        return "Hello World"; 
    }
}

will only work for 

http://localhost:8543/login/authenticate

You need to change your route prefix to

[RoutePrefix("api/login")]
public class LoginApi : ApiController
{
    //eg:POST api/login/authenticate.
    [HttpPost]
    [Route("authenticate")]
    public string Authenticate(LoginViewModel loginViewModel)
    {  
        return "Hello World"; 
    }
}

Upvotes: 3

thiag0
thiag0

Reputation: 2229

Your controller name "LoginApi" needs to end in "Controller" in order for the framework to find it. For example: "LoginController"

Here is a good article which explains routing in ASP.NET Web API: http://www.asp.net/web-api/overview/web-api-routing-and-actions/routing-in-aspnet-web-api

Upvotes: 9

Andy T
Andy T

Reputation: 9901

Notice you are using both attribute routing on the controller/action and convention routing with config.Routes.MapHttpRoute.

config.Routes.MapHttpRoute will map the routes as per your definition "api/{controller}/{id}".

While attribute routing, will map the routes based on how you've defined them: /login/authenticate.

Also, since you are using both attribute routing and convention routing, attribute routing takes presendence. I would stick to using one or the other. Having both adds a bit of confusion as to what route will be used to access an action method.

Upvotes: 0

Related Questions