Asp.net MVC routing ambiguous, two paths for same page

Question

I'm trying out ASP.NET MVC routing and have of course stumbled across a problem. I have a section, /Admin/Pages/, and this is also accessible through /Pages/, which it shouldn't. What could I be missing?

The routing code in global.asax:

public static void RegisterRoutes(RouteCollection routes)
{
        routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
        routes.MapRoute(
            "Pages",    // Route name
            "Admin/Pages/{action}/{id}",  // URL with parameters
            // Parameter defaults
            new { controller = "Pages", action = "Index", id = "" }  
        );

        routes.MapRoute(
            "Default",   // Route name
            "{controller}/{action}/{id}",   // URL with parameters
             // Parameter defaults
            new { controller = "Home", action = "Index", id = "" }  
        );

    }

Thanks!

Steve Morgan · Accepted Answer · 2008-09-16 08:36:06Z

7

I'd suggest adding an explicit route for /Pages/ at the beginning.

The problem is that it's being handled by the Default route and deriving:

controller = "Pages" action = "Index" id = ""

which are exactly the same as the parameters for your Admin route.

answered Sep 16, 2008 at 8:36

Steve Morgan

13.1k2 gold badges44 silver badges49 bronze badges

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

Comments

Haacked · Accepted Answer · 2008-09-18 16:02:15Z

7

For routing issues like this, you should try out my Route Debugger assembly (use only in testing). It can help figure out these types of issues.

P.S. If you're trying to secure the Pages controller, make sure to use the [Authorize] attribute. Don't just rely on URL authorization.

answered Sep 18, 2008 at 16:02

Haacked

59.3k14 gold badges94 silver badges115 bronze badges

1 Comment

an phu Over a year ago

This should be the answer because the intent is to secure the Index action method of the PagesController.

Garry Shutler · Accepted Answer · 2008-09-16 08:53:07Z

2

You could add a constraint to the default rule so that the {Controller} tag cannot be "Pages".

answered Sep 16, 2008 at 8:53

Garry Shutler

32.8k13 gold badges90 silver badges120 bronze badges

Comments

Hrvoje Hudo · Accepted Answer · 2008-09-17 07:02:18Z

0

You have in you first route {action} token/parameter which gets in conflict with setting of default action. Try changing parameter name in your route, or remove default action name.

answered Sep 17, 2008 at 7:02

Hrvoje Hudo

9,0345 gold badges35 silver badges42 bronze badges

Collectives™ on Stack Overflow

Asp.net MVC routing ambiguous, two paths for same page

4 Answers 4

Comments

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related