Url parameter not mapping

Question

I have the following method in my BlogController:

[HttpGet]
[Route("blog/search/{searchTag:string}")]
public ActionResult Search(string searchTag) {
    // Doing some search
}

I want my url to be for example blog/search/programming and this should get me to a page showing only the posts that are tagged with programming

I also have the following route:

routes.MapRoute(
    name: "BlogSearchRoute",
    url: "{controller}/{action}/{searchTag}",
    defaults: new { 
         controller = "Blog", 
         action = "Search" 
    }
);

Unfortunately my parameter doesn't map correctly and it is always null.

UPDATE
Additional information: here is my RouteConfig class:

public class RouteConfig
    {
        public static void RegisterRoutes(RouteCollection routes) {
            routes.LowercaseUrls = true;
            routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
            routes.IgnoreRoute("elmah.axd");              

            routes.MapRoute(
                name: "BlogSearchRoute",
                url: "{controller}/{action}/{searchTag}",
                defaults: new { controller = "Blog", action = "Search", searchTag = UrlParameter.Optional });

            routes.MapRoute(
                name: "BlogRoute",
                url: "{controller}/{action}/{id}/{title}",
                defaults: new { controller = "Blog", action = "Post", title = UrlParameter.Optional});

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

Less precise routes should normally be last. BlogSearchRoute is never used when it is after Default route. — AndreySarafanov
– AndreySarafanov, Commented Jun 29, 2015 at 15:18
Side notes: search text generally does not work as part of "path" segment of URI due to restrictions on characters allowed there; consider to specify explicit urls explicitly to minimize number of conflicts in the routing table: url: "blog/search/{searchTag}". Not directly related to your problem. — Alexei Levenkov
– Alexei Levenkov, Commented Jun 29, 2015 at 15:26

Mivaweb · Accepted Answer · 2015-06-29 15:19:25Z

1

In your custom route, define your searchTag as optional using:

routes.MapRoute(
    name: "BlogSearchRoute",
    url: "{controller}/{action}/{searchTag}",
    defaults: new { 
         controller = "Blog", 
         action = "Search",
         searchTag = UrlParameter.Optional
    }
);

UPDATE

You should define your Default route at the bottom under all your custom routes.

edited Jun 29, 2015 at 15:19

answered Jun 29, 2015 at 15:10

Mivaweb

5,7523 gold badges30 silver badges60 bronze badges

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

7 Comments

Martin Shishkov Over a year ago

That doesn't solve the problem... parameter is still null.

Mivaweb Over a year ago

And what if you remove the attribute [Route("blog/search/{searchTag:string}")] ? Because now you define the routes in your routings and as an attribute in your controller

Martin Shishkov Over a year ago

Still doesn't work. See the update, maybe that would help.

Mivaweb Over a year ago

Can you add your entire routeconfig.cs content?

Mivaweb Over a year ago

You have to place your default route at the bottom, now it will always use this route instead of your other custom routes

|

Martin Shishkov · Accepted Answer · 2015-06-29 16:13:58Z

0

I managed to get it working by removing BlogSearchRoute, the [Route()] attribute from my method and renaming searchTag to id

answered Jun 29, 2015 at 16:13

Martin Shishkov

2,8675 gold badges29 silver badges44 bronze badges

Comments

ce8 · Accepted Answer · 2022-07-28 19:24:05Z

0

Your route parameter {searchTag:string} has an incorrect constraint type. The ":string" constraint type does not exist and you should either remove the constraint type or take one of the valid ones that can be found in route constraints documentation.

answered Jul 28, 2022 at 19:24

ce8

231 silver badge3 bronze badges

Collectives™ on Stack Overflow

Url parameter not mapping

3 Answers 3

7 Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

7 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related