Localhost loopback do not work for the latest Edge 38.14393 under Windows 10 Enterprise .14393

By design Issue #10082889

Details

Author
Valera G.
Created
Dec 6, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

The problem/Critical bug:

Error: SCRIPT7002: XMLHttpRequest: Network Error 0x2efd, Could not complete the operation due to error 00002efd.

I have js code (Ajax request) that works in almost all modern browsers :
$.ajax({
type: "POST",
url: "http://localhost:12345/",

The request is sending to http server on localhost:12345.
about:flags: Developer settings:
"Allow localhost loopback (this might put your device at risk)" - checked (default)
(Http localhost server responses with patched header ‘Access-Control-Allow-Origin: *’)

It failed only for:

  • Win10 Enterprise [Version 10.0.14393] [1607 build 14393.447]
  • Microsoft Edge 38.14393.0.0
    Microsoft EdgeHTML 14.14393

But it worked for:

  • Windows 10 Pro : [Version 10.0.14393] [1607 build 14393.447]
  • (The same:) Microsoft Edge 38.14393.0.0
    Microsoft EdgeHTML 14.14393

Temporary workaround only for 10 Enterprise:

Run As Administrator:
CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe

The option "Allow localhost loopback (this might put your device at risk)" is ignored under 10 Enterprise! But it is working under 10 Pro. Obviously this is a bug.

Under Clear 10 Enterprise I have:
C:\Windows>CheckNetIsolation LoopbackExempt -s -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe
List Loopback Exempted AppContainers
[1] -----------------------------------------------------------------
Name: 001
SID: S-1-15-2-3624051433-2125758914-1423191267-1740899205-1073925389-3782572162-737981194-4256926629-1688279915-2739229046-3928706915
OK. 

Testing: Ajax request to localhost is working successfully for:

  • Surface 3 / Desktop Windows 10 Pro : [Version 10.0.14393] [1607 build 14393.447]
    Microsoft Edge 38.14393.0.0
    Microsoft EdgeHTML 14.14393

  • IE 11.447.14393.0 U11.0.37

  • Сhrome 54.0.2840.99 m

  • Firefox 50.0

Attachments

0 attachments

    Comments and activity

    • Win10 Enterprise has all the Windows Updates (“Your device is up to date”).

    • Microsoft Edge Team

      Changed Assigned To to “Shijun S.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Shijun S.” to “Venkat K.”

      Changed Status from “Confirmed”

    • Is there any news ?
      Let me know if you need anything else.

    • NEW TEST with AZURE:

      It’s working OK with AZURE Web ASP.NET APP . Edge allows access to http://localhost:/ .

      The problem is clear now: it is not working if Web ASP.NET site is running in local domain ! Edge doesn’t allow access to http://localhost:/

      NEW bug: developer.microsoft.com cut
      test:
      test http://localhost:/
      test http://localhost:/

    • < your port >

    • oh :(
      “<” your port “>”

    • Code

      // http://localhost:/
    • http://localhost:<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>> /

    • Bug! Fix this text editor with ‘less’ and ‘greater’ chars.

    • Working when I type URL directly:

      http://localhost:15480/logo
      

      But not working when I have the same thing in HTML code:

      This is broken in 38.14393 …

    • HTML code:

      <img src="http://localhost:15480/logo">
    • My CheckNetIsolation:

      CheckNetIsolation LoopbackExempt -s
      
      List Loopback Exempted AppContainers
      
      [1] -----------------------------------------------------------------
          Name: 005
          SID:  S-1-15-2-3624051433-2125758914-1423191267-1740899205-1073925389-3782572162-737981194-3859068477-1314311106-1651661491-1685393560
      
      [2] -----------------------------------------------------------------
          Name: 001
          SID:  S-1-15-2-3624051433-2125758914-1423191267-1740899205-1073925389-3782572162-737981194-4256926629-1688279915-2739229046-3928706915
      
      OK.
      
    • Microsoft Edge Team

      Changed Assigned To from “Venkat K.” to “Erik A.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “By design”

    • Your comments indicate that you are trying to do an XMLHttpRequest to a localhost URI from a page hosted on an internal domain. If the top-level page domain is an intranet host, we intentionally block access to loopback/localhost due to some esoteric security concerns. As noted in the FAQ at https://developer.microsoft.com/en-us/microsoft-edge/platform/faq/#how-can-i-debug-localhost, certain configurations may require you to change your firewall policies to allow intranet pages to also use loopback. Alternatively, if you can move your top-level page to a host treated as non-intranet, that will also allow this scenario to work.

      Thanks for your feedback!

    • We have a product that is served over the internet (not intranet) and interacts with a Windows Service that is installed on our end user’s systems. Our web page communicates with that service over https on an available port (typically 8080 or 8081) on 127.0.0.1 (localhost).

      Our organization has been able to reproduce this behavior in:

      • Windows 10 Pro 64-bit (10.0, Build 15063)
      • Microsoft Edge 40.15063.0.0
      • Microsoft EdgeHTML 15.15063

      and

      • Windows 10 Enterprise Version 1703 OS Build 15063.483
      • Microsoft Edge 40.15063.0.0
      • Microsoft EdgeHTML 15.15063

      We have also reproduced the behavior both on our internal office network, as well as external facing sites (our UAT environment not being accessed over VPN). It is reproducible regardless of the about:flags Developer Settings section’s “Allow localhost loopback” checkbox state. The only way we’ve been able to resolve the issue has been to run the command recommended in the link above as Administrator:

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

    You need to sign in to your Microsoft account to add a comment.

    Sign in