Summary:

LBS is not redirecting URLs that have forward slash in their name and that do not start with a protocol (scheme)
This cause a conflict with Enterprise Mode schema v.2 https://docs.microsoft.com/en-us/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance

Use case / Motivation:


1) LBS is not redirecting URLs that have forward slash in their name and that do not start with a protocol listed. 
However, the customer is using Microsoft tools with Enterprise Mode schema v.2 and LBS is not opening the sites they need, as the redirection is broken. 
2) As per Microsoft Post, it is not required to use protocol when using Enterprise Mode Schema https://docs.microsoft.com/en-us/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance. 
3) This also prevents us from using any Microsoft tools (Enterprise Mode Site List Manager and Enterprise Mode Site List Portal) to manage the Enterprise Mode List, as they all remove the protocol 

#See more information about steps to reproduce and workaround found by the customer. 

Example. 
-It redirects fine, 

<site url="www.woodgrovebank.com"> 
<compat-mode>default</compat-mode> 
<open-in>IE11</open-in> 
</site> 

-But not this: 

<site url="fabrikam.com/products"> 
<compat-mode>IE8Enterprise</compat-mode> 
<open-in>IE11</open-in> 
</site> 


Existing workarounds:

#All troubleshooting steps already taken/workaround: 

This causes an issue when we need to define a more specific URL to be in Enterprise mode, as adding the protocol does allow LBS to redirect the URL, but that breaks Enterprise Mode. The only way to get around this is to add the URL twice: 

To support Enterprise Mode: 

<site url="fabrikam.com/products"> 
<compat-mode>IE8Enterprise</compat-mode> 
<open-in>IE11</open-in> 
</site> 

Then to support LBS: 

<site url="https://fabrikam.com/products"> 
<compat-mode>IE8Enterprise</compat-mode> 
<open-in>IE11</open-in> 
</site> 


Case#: 17191284