A Major Facelift for the 404 Module
The 404 handler on EPiCode has been improved and upgraded for version 6 of EPiServer CMS. One of the new features is the ability for editors and administrators to maintain redirects through a gadget in the Online Center.
With the 404 Handler Redirect Gadget editors can add new custom redirects, delete or search for existing redirects. The "old URL" is unique, meaning that if you register two custom redirects with the same old URL, the latter will overwrite the first one. All redirects are saved in the Dynamic Data Store.
Installation and supported environments
You can choose between a NuGet install package (requires Visual Studio 2010) or a module install package for EPiServer Deployment Center. The NuGet package will become available in the EPiServer NuGet feed soon.
For download and documentation please visit the module wiki page on EPiCode.
The module has been developed and tested for IIS 7, and built using EPiServer CMS 6. I’ve briefly tested it on CMS 6 R2 and it seems to be working just fine. It has not been tested on .NET 4.
Awesome - really looking forward to trying this out (through Nuget of course!)
Does the redirect work in a similar way to Magnus' module (see below), which ensured the correct Http status code was also sent?
http://world.episerver.com/Blogs/Magnus-von-Wachenfeldt/Dates/2010/2/Making-EPiServer-and-Search-Engines-Work-Together/
Yes, if the url is mapped the Http 301 Moved Permanently is sent.
Update: The module is now available in the EPiServer NuGet Feed (http://nuget.episerver.com/).
Fantastic, so many people ask for this!
The correct HTTP status code isn't quite right when redirecting .aspx pages.
Instead you get a 302 returned for the old URL and then a redirect to the 404 page which then gives you a 301 code (see bottom of ticket code 198 https://www.coderesort.com/p/epicode/ticket/198#comment:1)
Does anyone have knowledge on what effect this will have with search engines?