Web API nested routing not working as expected

Question

I am having difficulty with a nested Web API routing set-up.

Given a routing config of:

config.Routes.MapHttpRoute(
    name: "UsersGroups",
    routeTemplate: "api/users/{userID}/groups/{groupID}",
    defaults: new { controller = "UsersGroups", groupID = UrlParameter.Optional }
);

and controller actions like thus:

public AuthGroup Get(long userID, int groupID)
{
     //Get specific group here
}

public IEnumerable<AuthGroup> Get(long userID)
{
    //get all groups for user here
}

Calling this route /api/users/1528/groups gives this error:

The parameters dictionary contains a null entry for parameter groupID of non-nullable type System.Int32 for method AuthGroup Get(Int64, Int32) in UsersGroupsController. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.

I was expecting it to grab the action with the single long parameter, but obviously for some reason it's ignoring this and going straight for the one with most arguments.

Based on what's available at MS on how Web API interprets routes: http://www.asp.net/web-api/overview/web-api-routing-and-actions/routing-and-action-selection I think what I have should be correct, but obviously it is not working as it seems like it should.

Paul Oliver · Accepted Answer · 2013-06-10 19:35:31Z

7

You should use RouteParameter.Optional (from Web API), not UrlParameter.Optional (from ASP.NET MVC).

Everything will behave as you want then.

More info:

UrlParameter.Optional - http://msdn.microsoft.com/en-us/library/system.web.mvc.urlparameter.optional(v=vs.108).aspx
RouteParameter.Optional - http://msdn.microsoft.com/en-us/library/system.web.http.routeparameter.optional(v=vs.108).aspx

edited Jun 10, 2013 at 19:35

Paul Oliver

7,7015 gold badges33 silver badges34 bronze badges

answered Jan 30, 2013 at 2:58

Filip W

27.2k6 gold badges97 silver badges82 bronze badges

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

1 Comment

jemerick Over a year ago

Absolutely right. My mistake was adding the route mappings in the MVC config section and then moving them later -- I picked up the UrlParameter.Optional and no matter how many times I looked at it I did not notice the difference. Thanks!

Collectives™ on Stack Overflow

Web API nested routing not working as expected

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related