Help shape the future of CMS PaaS release notes! Take this quick survey and share your feedback. 

Mari Jørgensen
Jun 1, 2011
  7310
(3 votes)

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. 

gadget

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.

Jun 01, 2011

Comments

Jun 1, 2011 04:04 PM

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/

Mari Jørgensen
Mari Jørgensen Jun 3, 2011 08:10 AM

Yes, if the url is mapped the Http 301 Moved Permanently is sent.

Mari Jørgensen
Mari Jørgensen Jun 3, 2011 02:28 PM

Update: The module is now available in the EPiServer NuGet Feed (http://nuget.episerver.com/).

Jun 10, 2011 02:34 AM

Fantastic, so many people ask for this!

rachel.goldthorpe@karuba.co.nz
rachel.goldthorpe@karuba.co.nz Feb 10, 2012 02:24 AM

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?

Please login to comment.
Latest blogs
Be careful with your (order) notes

This happened a quite ago but only now I have had time to write about it. Once upon a time, I was asked to look into a customer database (in a big...

Quan Mai | Feb 5, 2025 | Syndicated blog

Imagevault download picker

This open source extension enables you to download images as ImageData with ContentReference from the ImageVault picker. It serves as an alternativ...

Luc Gosso (MVP) | Feb 4, 2025 | Syndicated blog

Optimizely SaaS vs PaaS: A Comparison from Client and Developer Perspectives

Optimizely, one of the leading digital experience platform. Offering both Software-as-a-Service (SaaS) and Platform-as-a-Service (PaaS) solutions....

Praful Jangid | Feb 3, 2025

Returning to Optimizely After Many Years

Returning to Optimizely After Many Years: A Journey Through Its New Features After several years away from Optimizely’s Content Management … More

Jose Neto | Feb 2, 2025 | Syndicated blog