Suppose we want to have a route that allows an unbound number of segments like so:
We would need to add a route, normally at the end of the route table because this would probably catch all requests, like so:
routes.MapRoute("Final", "Route/{*segments}",
new { controller = "Product", action = "View" });
In the controller, an action that could handle this, could be:
public void ActionResult View(string[] segments /* <- the name of the parameter must match the name of the route parameter */)
{
// use the segments to obtain information about the product or category and produce data to the user
// ...
}