However, using CheckNetIsolation is pretty cumbersome-it requires that you know the AppContainer’s name or security ID, and you must configure each AppContainer individually. The post went on to explain how the CheckNetIsolation tool can be used to permit an AppContainer to send traffic to the local computer. This is, of course, problematic when debugging with Fiddler, as Fiddler is a proxy server which runs on the local computer. Immersive applications (and IE11 on Win8/8.1, not on Win10) run inside isolated processes known as “AppContainers.” By default, AppContainers are forbidden from sending network traffic to the local computer (loopback). UWP, including Edge) cannot access localhost by default. This is a Windows security policy: applications in Windows Runtime (aka. So this is a problem specific to one user and Edge, other programs or users don't have this problem.Īny ideas what else I can do to diagnose this? Using the same Windows Proxy settings as for the user which doesn't have the problem.Restarting the Network List Service and the Network Location Awareness service.What I tried but not solving the problem: Using Edge with my user but using localhost or an IP address either 127.0.0.1 or .x.Using Edge on the same machine but with a different user.Using Edge from another machine on the local network.Using Firefox, Chrome, IE-11 and Command Line tools on the local machine.The F12 Network Tab doesn't show anything. Make sure that you’ve got the right web address: When opening the site in Microsoft Edge I get this message: I have a local IIS running, with a binding like the hostname is listed in an external DNS server and name resolution works fine.
0 kommentar(er)
