A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Johan Björnfot
Sep 8, 2014
  6210
(0 votes)

Changes in simple address routing

In package EPiServer.CMS.Core.7.13.3 we have solved an issue that causes a slightly different behaviour in how simple addresses are routed. As a background: for “ordinary” content routing we introduced a more strict handling in 7.5 where for example it was not possible to have a language segment specifying one language while the segment it self was on a content instance on another language. Like for example:

http://mysite/en/produkter (where “produkter” is the segment on the swedish version)

In CMS 7 that was possible to route and resulted in the english version of the page. In CMS 7.5 that results in a 404. We also introduced a configuration setting strictLanguageRouting that can be set to false to get the more tolerant behaviour as in CMS 7.

Now we have also changed simple address routing so it is more strict. So given that a page exist in both language "en" and language "sv" and has simple addresses "ensimple" and "svsimple" the following scenarios apply. For those scenarios that differs from previous version a parenthesis is added describing the old behaviour:

No host language mapping, strictLanguageRouting=true

  1. http://sitehost/ensimple => english page

  2. http://sitehost/svsimple => swedish page

  3. http://sitehost/en/ensimple => english page

  4. http://sitehost/sv/svsimple => swedish page

  5. http://sitehost/sv/ensimple => 404 (this gave swedish page in previous version)

No host language mapping, strictLanguageRouting=false

  1. http://sitehost/ensimple => english page

  2. http://sitehost/svsimple => swedish page

  3. http://sitehost/en/ensimple => english page

  4. http://sitehost/sv/svsimple => swedish page

  5. http://sitehost/sv/ensimple => swedish page

Host "sitehost" mapped to language "en", strictLanguageRouting=true

  1. http://sitehost/ensimple => english page

  2. http://sitehost/svsimple => 404 (this gave english page in previous version)

  3. http://sitehost/en/ensimple => 404 (this gave english page in previous version)

  4. http://sitehost/sv/svsimple => swedish page

  5. http://sitehost/sv/ensimple => 404 (this gave swedish page in previous version)

Host "sitehost" mapped to language "en", strictLanguageRouting=false

  1. http://sitehost/ensimple => english page

  2. http://sitehost/svsimple => swedish page

  3. http://sitehost/en/ensimple => english page

  4. http://sitehost/sv/svsimple => swedish page

  5. http://sitehost/sv/ensimple => swedish page

To get the more tolerant behaviour as in previous versions you can either set the strictLanguageRouting attribute (on configuration element applicationSettings) to false. That will however not only affect simple address but also "ordinary" routing so it works as in EPiServer 7. To only affect simple address you could have an initialization module that configures simple address routing to not use strict language routing as the following code:

using EPiServer.Framework;
using EPiServer.Web.Routing;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;

namespace MvcPreview
{
    [InitializableModule]
    public class SimpleAddressModule : IInitializableModule
    {
        public void Initialize(EPiServer.Framework.Initialization.InitializationEngine context)
        {
            EPiServer.Global.RoutesRegistered += delegate(object source, RouteRegistrationEventArgs args)
            {
                var simpleAddressRoute = args.Routes.OfType<ContentRoute>().FirstOrDefault(r => r.Name.Equals("simpleaddress"));
                if (simpleAddressRoute != null)
                {
                    simpleAddressRoute.StrictLanguageRoutingResolver = () => false;
                }
            };
        }

        public void Preload(string[] parameters)
        {
        }

        public void Uninitialize(EPiServer.Framework.Initialization.InitializationEngine context)
        {
        }
    }
}
Sep 08, 2014

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026