This article has not yet been verified against Umbraco 8.
The concepts and code examples might not work if you are running Umbraco 8.0 or a later version. If you are using Umbraco 7, this article is perfect for you!
You are more than welcome to report any issues found on the Documentation Issue Tracker.
Obsolete. The concept of NotFoundHandlers has been replaced by Content Finders
Configuration file for legacy NotFoundHandlers. These are used to register custom code within the Umbraco incoming request pipeline, including the legacy way to handle a custom 404 error.
The Default Handlers are listed in this configuration file for 'backwards compatibility':
<NotFoundHandlers> <notFound assembly="umbraco" type="SearchForAlias" /> <notFound assembly="umbraco" type="SearchForTemplate"/> <notFound assembly="umbraco" type="SearchForProfile"/> <notFound assembly="umbraco" type="handle404"/> </NotFoundHandlers>
If you upgrade from an older version of Umbraco then legacy NotFoundHandlers listed here 'should' still work. The request pipeline contains a ContentFinderByNotFoundHandlers IContentFinder that will attempt to execute the functionality of any legacy NotFoundHandlers, but it's recommended to move your custom request handling logic to IContentFinders.
Implementing 404 not found properly
Custom 404's are now handled within a custom IContentFinder by setting the Is404 property to true for the PublishedContentRequest processed by the IContentFinder or by registering the IContentFinder as a ContentLastChanceFinder - Using an IContentFinder for Custom 404s