Correct me on URL routing in MVC issue

Question

This is related my question which i asked in this link correct me on url routing in mvc

Now i came with another problem, so i thought i will ask it as new question.

Now i have following routes in my global.asax file

routes.MapRoute(
           "Custom", // Route name
           "{action}/{id}", // URL with parameters
           new { controller = "Authentication", action = "BigClientLogin", id = UrlParameter.Optional } // Parameter defaults
       );

and

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

Now what happens is when i run my solution the URL i am getting is http://localhost:65423/Login this is what i need for my Login Page that is OK. But when i login in as user i am getting "The resource cannot be found" error.

when i checked it i can see that my URL is now changed to http://localhost:65423/Admin/Dashboard

So i think this causing the issue. So this looks the problem related to my global.asax routing.

Can anyone help me to find out what i did wrong.

Assuming you've read how routing works (i.e. [ScottGu article](http://weblogs.asp.net/scottgu/asp-net-mvc-framework-part-2-url-routing)) and looked at answers to your previous question - could you please explain what do you expect from 2 routes that match the same set of paths and how behavior of the code is different from your expectation? — Alexei Levenkov, Jan 26 '15 at 17:31
@alexi thanks for replying. There was slight change in my question. I was actually confused on which route format should I use. Actually my client requirement is that their login page url shoul look like http://localhost:65423/Login this. So I was managed to cReate it using first route format. But once I logged in no actions are recognizing due to first route format. But if i am using second route format it will work perfectly even after login. But that time my first condition will not satisfy. — Nithin Paul, Jan 26 '15 at 19:58

NightOwl888 · Answer 1 · 2018-02-04T16:53:19.283

You have 2 routes with completely optional segments. The issue is that there is no way for the routing framework to differentiate between them.

The only way you can make it work with your existing routes is to specify them explicitly by name (such as when using @Html.RouteLink or @Html.RouteUrl).

@Html.RouteLink("Custom Link 1", "Custom", new { action = "BigClientLogin" })
@Html.RouteLink("Custom Link 2", "Custom", new { action = "Action2" })
@Html.RouteLink("Home Page", "Default", new { controller = "Home", action = "Index" })
@Html.RouteLink("About", "Default", new { controller = "Home", action = "About" })

Doing it that way will function, but is not normal. Typically, there is only one route configured with all defaults for the controller, action, and id and the rest have some explicitly declared segments and/or constraints (segments being preferable).

routes.MapRoute(
   "Custom", // Route name
   "Custom/{action}/{id}", // URL with parameters
   new { controller = "Authentication", action = "BigClientLogin", id = UrlParameter.Optional } // Parameter defaults
);

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

The first route will now only match when the URL starts with /Custom/. If it does not start with custom, it will match the default route.

The trick is to ensure that the routes are listed in the right order and that they only match the URL in specific cases, letting them pass on to the next route in the list if the case is not correct.

score 0 · Answer 2 · answered Feb 04 '18 at 17:09

It happens because of 2 things. 1st the sequence of Your route 2nd your defaults

So if you end up on 'admin/dashboard' that's not a default, guess you've just put it in your studio to start there?

To get to http://localhost:65423/Login you'll need an action on Your AuthenticationController called 'Login' but it looks like the one You have configured is 'BicClientLogin' so You won't be taken to login unless you specify it, and at that time it has to exist.

To Help You further we need to know what controllers You have and what actions there exists, plus if security is part of your solution and if in case, what is is set to use.

Correct me on URL routing in MVC issue

2 Answers2

Linked