Debugging with the Local Machine IP in Microsoft Edge

Some developers testing LEADTOOLS web applications with Microsoft Edge may encounter a problem when using Microsoft Edge to test applications hosted on their development machine. Edge runs as a Windows modern application, and thus has network isolation for security reasons. For developers using LEADTOOLS, this could mean trouble when using localhost to access a local web server hosting HTML5/JS applications or web services.

More information about this problem can be found on the MSDN under the blog post entitled How to Debug Localhost on Microsoft Edge, and the topic entitled How to Enable Loopback and Troubleshoot Network Isolation (Windows Runtime applications).

This issue does not appear to occur with all Windows 10 machines. In our testing, early builds of Windows 10 did not exhibit this issue, but now using later builds we are able to duplicate it. This could change again after future updates from Microsoft.

The above article recommends running the following command in Windows 10 build 10158 or newer:

CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe" 
             

In our search of the Windows Registry, we found what we believe may be a blacklist for Edge under the following registry key:

[HKEY_CURRENT_USER\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\microsoft.microsoftedge_8wekyb3d8bbwe\MicrosoftEdge\TabProcConfig]