ASP.NET MVC: url routing vs querystring

pistacchio picture pistacchio · Jun 9, 2009 · Viewed 42.3k times · Source

I have a page routed like /Comments/Search/3 where i search and display all the comments of the thread "3".

I'm adding a sort function (by date, author etc). What is the best way to handle it? /Comments/Search/3/Sort/Author or /Comments/Search/3?sort=author ?

How do I automatically handle the querystring sort=author as a parameter in MVC?

Thanks

Answer

Praveen Angyan picture Praveen Angyan · Jun 9, 2009

I prefer: /Comments/Search/3?sort=author. The querystring is a good place to pass in programmatic parameters, especially if the parameter (like in this case) is not important for SEO purposes. If the parameter had some semantic meaning as a search term, the first URL would be better.

In a controller method you can use something like this:

public ActionResult Search(int id, string sort)

ASP.NET MVC will automatically wire up querystring values to the parameters of your method.

Use the following route

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

/Comments/Search/3?sort=author will call Search(3, "author")

/Comments/Search/3 will call Search(3, null)

Keep in mind that id is mandatory so this url will fail: /Comments/Search