Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more

Johan Björnfot
Sep 8, 2014
  6115
(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
Optimizely Configured Commerce and Spire CMS - Figuring out Handlers

I recently entered the world of Optimizely Configured Commerce and Spire CMS. Intriguing, interesting and challenging at the same time, especially...

Ritu Madan | Mar 12, 2025

Another console app for calling the Optimizely CMS REST API

Introducing a Spectre.Console.Cli app for exploring an Optimizely SaaS CMS instance and to source code control definitions.

Johan Kronberg | Mar 11, 2025 |

Extending UrlResolver to Generate Lowercase Links in Optimizely CMS 12

When working with Optimizely CMS 12, URL consistency is crucial for SEO and usability. By default, Optimizely does not enforce lowercase URLs, whic...

Santiago Morla | Mar 7, 2025 |

Optimizing Experiences with Optimizely: Custom Audience Criteria for Mobile Visitors

In today’s mobile-first world, delivering personalized experiences to visitors using mobile devices is crucial for maximizing engagement and...

Nenad Nicevski | Mar 5, 2025 |

Unable to view Optimizely Forms submissions when some values are too long

I discovered a form where the form submissions could not be viewed in the Optimizely UI, only downloaded. Learn how to fix the issue.

Tomas Hensrud Gulla | Mar 4, 2025 |

CMS 12 DXP Migrations - Time Zones

When it comes to migrating a project from CMS 11 and .NET Framework on the DXP to CMS 12 and .NET Core one thing you need to be aware of is the...

Scott Reed | Mar 4, 2025