CODEWITHSUNDEEP
c#asp.netasp.net-mvcasp.net-web-api
Suneel Dixit
Suneel Dixit

Reputation: 889

ASP.NET MVC WebAPI 404 error

I have an asp.net web forms application running under v4.0 integrated mode.

I tried to add an apicontroller in the App_Code folder.

In the Global.asax, I added the following code

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

When I tried to navigate to the controller at http://localhost/api/Value, I get the 404 error.

The extensionless url is configured in the handler section. I have forms and anonymous authentication enabled for the website.

ExtensionLess url is configured for '*.'

When I hit the url for controller, the request is handled by StaticHandler instead of ExtensionlessUrlHandler-Integrated-4.0.

I have no clue now why the system will throw the error as shown in the image below. Error

Upvotes: 62

Views: 96044

Answers (20)

Martin L.
Martin L.

Reputation: 141

Thanks to Shannon, ceinpap, and Shri Guru, the following modification works for me:

  1. WebApiConfig.cs:

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

  2. Global.asax.cs:

    protected void Application_Start()
{
    ...
    GlobalConfiguration.Configure(WebApiConfig.Register);
    RouteConfig.RegisterRoutes(RouteTable.Routes);
    ...
}

Upvotes: 2

chaitanyasingu
chaitanyasingu

Reputation: 141

The sequence of registering the route, was the issue in my Application_Start(). the sequence which worked for me was 

AreaRegistration.RegisterAllAreas();
GlobalConfiguration.Configure(WebApiConfig.Register);
RouteConfig.RegisterRoutes(RouteTable.Routes);

earlier it was

AreaRegistration.RegisterAllAreas();
RouteConfig.RegisterRoutes(RouteTable.Routes);
GlobalConfiguration.Configure(WebApiConfig.Register);

Upvotes: 1

Shri Guru
Shri Guru

Reputation: 41

After hours of spending time on this , i found the solution to this in my case.

It was the order of registering the Routes in RouteConfig .

We should be registering the HttpRoute in the Route table before the Default controller route . It should be as follows. Route Config Route table configuration

  public class RouteConfig
{
    public static void RegisterRoutes(RouteCollection routes)
    {
        routes.MapHttpRoute(
             name: "DefaultApi",
             routeTemplate: "api/{controller}/{action}/{id}",
             defaults: new { id = RouteParameter.Optional }
         );
        routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

        routes.MapRoute(
            name: "Default",
            url: "{controller}/{action}/{id}",
            defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
        );

    }
}

Upvotes: 2

aoakeson
aoakeson

Reputation: 602

In my case I forgot to make it derive from ApiController.

So it would look like 

public class ValuesController : ApiController

Upvotes: 0

Lari Tuomisto
Lari Tuomisto

Reputation: 308

I appreciate this is a very old question but I thought I would add another answer for future users.

I found this to happen just now in a project I was working on only after it was deployed to CI/Staging. The solution was to toggle the compilation debug="true" value back and forth while deploying each version to each environment once, and it would fix itself for me.

Upvotes: 0

ceinpap
ceinpap

Reputation: 41

Thanks Shannon, works great =>

My order in my Global.asax was :

GlobalConfiguration.Configure(WebApiConfig.Register);  
RouteConfig.RegisterRoutes(RouteTable.Routes);

instead of the good one : 

RouteConfig.RegisterRoutes(RouteTable.Routes);
GlobalConfiguration.Configure(WebApiConfig.Register);

Upvotes: 4

Eric Herlitz
Eric Herlitz

Reputation: 26257

We had this as well, changing .NET version from 4.5 to 4.5.1 or newer solved the issue

Upvotes: 1

tcb
tcb

Reputation: 4604

I copied a RouteAttribute based controller dll into the bin folder, but it wasn't getting recognized as a valid controller and I was getting the 404 error on the client.

After much debugging, I found my problem. It was because the version of System.Web.Http.dll that the controller was referencing was different from the version of System.Web.Http.dll that the main project (the one containing global.asax.cs) was referencing.

Asp.Net finds the controller by reflection using code like this

internal static bool IsControllerType(Type t)
{
    return
        t != null &&
        t.IsClass &&
        t.IsVisible &&
        !t.IsAbstract &&
        typeof(IHttpController).IsAssignableFrom(t) &&
        HasValidControllerName(t);
}

Since IHttpController is different for each version of System.Web.Http.dll, the controller and the main project have to have the same reference.

Upvotes: 1

Mansfield
Mansfield

Reputation: 15140

Time for me to add my silly oversight to the list here: I mistyped my webapi default route path.

Original:

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

Fixed: (observe the curly braces around "id")

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

Upvotes: 0

Tiago Gouvêa
Tiago Gouvêa

Reputation: 16740

None of solutions above solved my problem... My error was that I copied the bin files directly to production server, and then, I don't work. The 404 was gone when I publish the project to disk and copied the "published" folder to server. It's a little obvious, but, can help some one.

Upvotes: 1

Sbu
Sbu

Reputation: 940

Also try to delete your entire api bin folder's content. Mine was containing old dlls (due to a big namespace renaming) exposing conflicting controllers. Those dll weren't deleted by Visual Studio's Clean functionality.

(However, I find asp.net web api seriously lacks routing and debugging information at the debugging level).

Upvotes: 3

Alan
Alan

Reputation: 183

I tried all of the above and had the same problem. It turned out that the App pool created in IIS defaulted to .net 2.0. When I changed it to 4.0 then it worked again

Upvotes: 7

shannon
shannon

Reputation: 8774

I was experiencing this problem.

I tried editing my WebApiConfig.cs to meet a number of recommendations here and code samples elsewhere. Some worked, but it didn't explain to why the route was not working when WebApiConfig.cs was coded exactly as per the MS template WebApi project.

My actual problem was that in manually adding WebApi to my project, I had not followed the stock order of configuration calls from Global.asax

    protected void Application_Start()
    {
        AreaRegistration.RegisterAllAreas();
        // This is where it "should" be
        GlobalConfiguration.Configure(WebApiConfig.Register);
        FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
        RouteConfig.RegisterRoutes(RouteTable.Routes);
        // The WebApi routes cannot be initialized here.
        BundleConfig.RegisterBundles(BundleTable.Bundles);
    }

I could make guesses about why this is, but I didn't investigate further. It wasn't intuitive to say the least.

Upvotes: 116

Eric W.
Eric W.

Reputation: 7992

Also, make sure your controller ends in the name "Controller" as in "PizzaPieController".

Upvotes: 11

Alborz
Alborz

Reputation: 6903

The problem is in your routing configuration. Mvc routing is different from WebApi routing.

Add reference to System.Web.Http.dll, System.Web.Http.Webhost.dll and System.Net.Http.dll and then configure your API routing as follows: 

   GlobalConfiguration.Configuration.Routes.MapHttpRoute(
     name: "DefaultApi",
     routeTemplate: "api/{controller}/{id}",
     defaults: new { id = System.Web.Http.RouteParameter.Optional }
   );

Upvotes: 32

crunchy
crunchy

Reputation: 703

If you create the controller in App_Code how does the routing table know where it is? You have specified the route as "api/{controller/..." but that's not where the controller is located. Try moving it into the correct folder.

Upvotes: 2

dbalogh
dbalogh

Reputation: 226

Your route configuration looks good. Double check the handlers section in web.config, for integrated mode this is the proper way to use ExtensionLessUrlHandler:

<add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />

More on this topic: http://blogs.msdn.com/b/tmarq/archive/2010/05/26/how-extensionless-urls-are-handled-by-asp-net-v4.aspx

Upvotes: 0

Binson Eldhose
Binson Eldhose

Reputation: 749

Ensure the following things

1.) Ensure that your IIS is configured with .NET 4.5 or 4.0 if your web api is 4.5 install 4.5 in IIS

run this command in command prompt with administrator privilege

C:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis.exe -i

2.) Change your routing to 

RouteTable.Routes.MapHttpRoute(
      name: "DefaultApi",
      routeTemplate: "{controller}/{id}",
      defaults: new { id = System.Web.Http.RouteParameter.Optional }
 );

and make request with Demo/Get (where demo is your controller name)

if the 1,2 are not working try 3

3.) Add following configuration in web.config file

<system.webServer>
    <modules runAllManagedModulesForAllRequests="true" />

</system.webServer>

Upvotes: 17

volpav
volpav

Reputation: 5128

For the URL you've trying (http://localhost/api/Value) make sure there's a public type named ValueController which derives from ApiController and has a public method with some of these characteristics:

  • Method name starts with Get (e.g. GetValues or simply Get).
  • There's an HttpGet attribute applied to the method.

In case you're trying the code from the default Web API project template, the name of the controller is ValuesController, not ValueController so the URL will be http://localhost/api/values.

If non of the above helps, you may want to enable tracing which can give you a useful insight on where in the pipeline the error occurs (as well as why).

Hope this helps.

Upvotes: 1

Karl Anderson
Karl Anderson

Reputation: 34846

Try just using the Value part of the controller name, like this:

http://localhost/api/Value

Note: By convention, the routing engine will take a value passed as a controller name and append the word Controller to it. By putting ValueController in the URI, you were having the routing engine look for a class named ValueControllerController, which it did not find.

Upvotes: 0

Related Questions