Custom routing in Umbraco

There are a couple of ways of controlling the routing behavior in Umbraco: customizing how the inbound request pipeline
finds content & creating custom MVC routes that integrate within the Umbraco pipeline

Customizing the inbound pipeline

Below lists the ways in which you can customize the inbound request pipeline, this is done by using native Umbraco plugin classes, events or defining your own routes.

IContentFinder

All Umbraco content is looked up based on the URL in the current request using an IContentFinder. IContentFinder's are quite easily to create and implement on your own which will allow you to map any URL to an Umbraco content item.

Last Chance IContentFinder

A 'Last Chance' IContentFinder is a special implementation of an IContentFinder for use with handling 404's. You can implement one of these plugins to decide which Umbraco content page you would like to show when the URL hasn't matched an Umbraco content node.

To set your own 404 finder create an IContentFinder and set it as the ContentLastChanceFinder. A ContentLastChanceFinder will always return a 404 status code. Example:

Custom MVC routes

You can specify your own custom MVC routes to work within the Umbraco pipeline. This requires you to use an implementation of Umbraco.Web.Mvc.UmbracoVirtualNodeRouteHandler with your custom route.

As an example:

//custom route to MyProductController which will use a node with ID 1234 as the// IPublishedContent for the current rendering page
routes.MapUmbracoRoute(
"test",
"Products/{action}/{sku}",
new
{
controller = "MyProduct",
sku = UrlParameter.Optional
},
new UmbracoVirtualNodeByIdRouteHandler(1234));

Our.umbraco.com is the community mothership for Umbraco, the open source asp.net cms. With a friendly forum for all your questions, a comprehensive documentation and a ton of packages from the community.
This site is running
Umbraco version 7.13.1