Removing port 443 from urls generated by Sitecore

For as long as I’ve been working on Sitecore there has been this really annoying issue where setting the link manager to include server url and running under https will cause urls to be generated with the port number included. e.g. https://www.himynameistim.com:443/ which naturally you don’t actually want.

Aside: This issue was finally fixed in Sitecore 9.1

To overcome this there are a few methods you can take.

Method 1 – Set the Scheme and Port on you site defenition

This is possibly the smallest change you can make as it’s just 2 settings in a config file.

Setting the external port on site node to 80 (yes 80) tricks the link manager code into not appending the port number as it does it for everything other than port 80.

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"&gt;
  <sitecore&gt;
    <sites xdt:Transform="Insert"&gt;
      <site name="website"&gt;
        <patch:attribute name="hostName"&gt;www.MySite.com</patch:attribute&gt;
        <patch:attribute name="rootPath"&gt;/sitecore/content/MySite</patch:attribute&gt;
        <patch:attribute name="scheme"&gt;https</patch:attribute&gt;
        <patch:attribute name="externalPort"&gt;80</patch:attribute&gt;
      </site&gt;     
    </sites&gt;
  </sitecore&gt;
</configuration&gt;

What I don’t like about this method though, is your setting something to be wrong to get something else to come out right. It’s all a bit wrong.

Method 2 – Write your own link provider

The second method which I have generally done is to write your own provider which strips the port number off the generated URL.

For this you will need:

1. A patch file to add the provider:

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"&gt;
  <sitecore&gt;
    <linkManager defaultProvider="sitecore"&gt;
      <patch:attribute
          name="defaultProvider"
          value="CustomLinkProvider" /&gt;
      <providers&gt;
        <add name="CustomLinkProvider"
             type="MySite.Services.CustomLinkProvider, 
                         MySite"
                       languageEmbedding="never"
                       lowercaseUrls="true"
                       useDisplayName="true"
                       alwaysIncludeServerUrl="true"
          /&gt;
      </providers&gt;
    </linkManager&gt;
    <mediaLibrary&gt;
      <mediaProvider&gt;
        <patch:attribute name="type"&gt;
          MySite.Services.NoSslPortMediaProvider, MySite
        </patch:attribute&gt;
      </mediaProvider&gt;
    </mediaLibrary&gt;
  </sitecore&gt;
</configuration&gt;

2. A helper method that removes the ssl port

namespace MySite
{
    /// <summary&gt; 
    /// Link Helper is used to remove SSL Port 
    /// </summary&gt; 
    public static class LinkHelper
    {
        /// <summary&gt; 
        /// This method removes the 443 port number from url 
        /// </summary&gt; 
        /// <param name="url"&gt;The url string being evaluated</param&gt; 
        /// <returns&gt;An updated URL minus 443 port number</returns&gt; 
        public static string RemoveSslPort(string url)
        {
            if (string.IsNullOrWhiteSpace(url))
            {
                return url;
            }

            if (url.Contains(":443"))
            {
                url = url.Replace(":443", string.Empty);
            }

            return url;
        }
    }
}

3. The custom link provider which first gets the item url the regular way and then strips the ssl port

using Sitecore.Data.Items;
using Sitecore.Links;

namespace MySite
{
    /// <summary&gt;Provide links for resources.</summary&gt; 
    public class CustomLinkProvider : LinkProvider
    {
        public override string GetItemUrl(Item item, UrlOptions options)
        {
            // Some code which manipulates and exams the item...

            return LinkHelper.RemoveSslPort(base.GetItemUrl(item, options));
        }
    }
}

4. The same provider for media

using Sitecore.Data.Items;
using Sitecore.Resources.Media;

namespace MySite
{
    /// <summary&gt; 
    /// This method removes SSL port number from Media Item URLs 
    /// </summary&gt; 
    public class NoSslPortMediaProvider : MediaProvider
    {
        /// <summary&gt; 
        /// Overrides Url mechanism for Media Items 
        /// </summary&gt; 
        /// <param name="item"&gt;Sitecore Media Item</param&gt; 
        /// <param name="options"&gt;Sitecore Media Url Options object</param&gt; 
        /// <returns&gt;Updated Media Item URL minus 443 port</returns&gt; 

        public override string GetMediaUrl(MediaItem item, MediaUrlOptions options)
        {
            var mediaUrl = base.GetMediaUrl(item, options);
            return LinkHelper.RemoveSslPort(mediaUrl);
        }
    }
}

What I don’t like about this method is it’s messy in the opposite way. The port number is still being added, and we’re just adding code to try and fix it after.

Credit to Sabo413 for the code in this example

Method 3 – Official Sitecore Patch

Given that it’s Sitecore’s bug, it does actually make sense that they fix it. After all people are paying a license fee for support! This simplifies your solution down to 1 extra patch file and a dll. What’s better is as it’s Sitecores code they have the responsibility of fixing it, if it ever breaks something, and you have less custom code in your repo.

You can get the fix here for Sitecore version 8.1 – 9.0.

So this may leave you wondering how did Sitecore fix it? Well having a look inside the dll reveals they wen’t for method 2.