Deane Barker
May 14, 2010
  12482
(4 votes)

Redirecting to a Simple Address

I was doing an EPiServer demo the other day, and was the showing the “simple address” feature that lets you map pages to simple URLs like “/register” or “/info.”

The client asked if those simple URLs could redirect rather than rewrite.  At the default, if you map a page to a simple address, it’s available both at that URL and its normal URL further down in the tree.  This could be problematic for some organizations to have duplicate content at two URLs.

Just for fun, I set out to solve the problem, and managed to bang it out in a dozen lines of code (most of it error checking).

The timing of where the code runs is a little tricky.  I thought about writing an HttpModule for it, but I needed to have the EPiServer page in hand when the code ran.  So, I need to run this code before anything on the page runs, but after the EPiServer content is mapped to the incoming request.  And it obviously need to run on every page, so I was looking for a way to catch the first moment we’re sure the visitor wants an EPiServer content object.

The method I used was to write a PagePlugin that hooks into the Init event of the page, like this:

public static void Initialize(int optionFlag)
{
    PageBase.PageSetup += new PageSetupEventHandler(PageSetup);
}

public static void PageSetup(PageBase sender, PageSetupEventArgs e)
{
    sender.Init += new EventHandler(CheckForSimpleAddressAccess);
}

What we’ve done with this is hooked an event very early into the page lifecycle.  This runs before anything in the actual page code-behind, so we can essentially pre-empt the entire page execution.

After checking that we’re on a TemplatePage with a valid (non-null) EPiServer page, I check to see if the RawUrl is the same as the simple address for the page.  If it is, I assume they came in on the simple address and redirect them to the real address.  The code for this is pretty simple:

if (String.Concat("/", (sender as PageBase).CurrentPage.Property["PageExternalURL"].ToString()) == HttpContext.Current.Request.RawUrl)
{
    Http.Current.Response.Redirect((sender as PageBase).CurrentPage.StaticLinkURL, true);
}

I took it one step further and added the ability to have a “Redirect to Simple Address” checkbox, so you can select whether a simple address will act as a rewrite or a redirect on a page-by-page basis.  If that doesn’t interest you, it should be pretty simple to comment those lines out and just have this code execute in all cases.

Just a quick warning: this code tested fine, but has not been implemented in any actual environment (I was just solving a problem for fun, remember), so should not be considered production-ready.  If you find any bugs, drop me an email.

Here’s the download.  The zip contains a single class file.  Compile it into your project.

May 14, 2010

Comments

Jeff Wallace
Jeff Wallace Sep 21, 2010 10:33 AM

Haven't tested it yet but it looks like nice work. :)

Ben Nitti
Ben Nitti Jun 24, 2020 09:41 PM

This would be great.  Ths download link is returning 404. Do you still have this code available?

Please login to comment.
Latest blogs
Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 1 of 2)

How Niteco's Upgrade Machine   uses orchestrated AI coding agents to deliver a buildable baseline and a running CMS, then hands over for...

Hung Le Hoang | May 11, 2026

Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |

Optimizely SaaS CMS Developer Certification Exam

The Optimizely SaaS CMS Developer Certification is an industry-recognized credential for developers and architects who build scalable, composable...

Megha Rathore | May 5, 2026