Question

I have two very simple routes

       routes.MapRoute(
            "post", // Route name
            postPage + "/{slug}", // URL with parameters
            new { controller = "Home", action = "Article" } // Parameter defaults
        );

        routes.MapRoute(
            "page", // Route name
            "{slug}", // URL with parameters
            new { controller = "Home", action = "Page", slug = homePage} // Parameter defaults
        );

And here is my controller logic

    public ActionResult Article(string slug)
    {
        return View(repo.GetPost(slug));
    }

    public ActionResult Page(string slug)
    {
        if (slug.ToLower() == MetaData.PostsPage.ToLower())
            return View("listPosts", repo.GetAllPosts());
        else
            return View("page", repo.GetPage(slug));
    }

homePage and postPage are set from value’s in the database. Allowing the user to define the default page as well as the page to show posts.

My issue occurs when adding an area named “Admin”. I get a controller added to my RouteTable

    context.MapRoute(
            "Admin_default",
            "Admin/{controller}/{action}/{id}",
            new { action = "Index", id = UrlParameter.Optional }
        );

Now when a user Access Admin/Account/Logon the page loads fine, but my debugger still tries to go into the Home controller and the Page action. But the RouteDebugger says it doesn’t match the current request. I’m puzzled on how to fix this.

RouteDebugger screenshot: https://i.stack.imgur.com/7cpHm.png
Debugger going into my HomeControler Page AtionResult: https://i.stack.imgur.com/uSJBK.png

Answer 1

I found out the issue.

I had a favicon.ico set in the main area of my site, but not the Admin area.
So when I went to the Admin area the browser made a request for favicon.ico that got picked up by that route. Thats why my routes looked fine in the RouteDebugger, because they were.

Thanks for the help Kundan!