Cannot connect to local website that is in the Intranet or Trusted zones from Edge using FQDN or loopback address

Confirmed Issue #8888023 • Assigned to Forbes H.

Details

Author
Greg M.
Created
Sep 13, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Unable to access a local web application in Edge on Windows 10 that is in the Intranet or Trusted zone when the URL contains the FQDN or loopback address (127.0.0.1). For reference, I am testing with the below URL formats that are all valid for the local site:

https://localhost:<port>/<restofurl>.html ***** Always works
http://localhost:<port>/<restofurl>.html ***** Always works
https://MyHostName:<port>/<restofurl>.html ***** Always works
http://MyHostName:<port>/<restofurl>.html ***** Always works
https://MyHostName.mydomain.com:<port>/<restofurl>.html ***** Only works in Internet and Restricted zones
http://MyHostName.mydomain.com:<port>/<restofurl>.html ***** Only works in Internet and Restricted zones
https://127.0.0.1:<port>/<restofurl>.html ***** Only works in Internet and Restricted zones
http://127.0.0.1:<port>/<restofurl>.html ***** Only works in Internet and Restricted zones

Using Edge, I can only connect using the hostname only or localhost URLs when in the Intranet and Trusted zones. All versions of the URL work in Edge when in the Internet or Restricted zones. All versions of the URL work in IE11 in the Internet, Intranet, Trusted, and Restricted zones. All URLs work for Firefox and Chrome. This appears to only affect displaying a local website in the Intranet and Trusted zones using the FQDN or loopback address in the URL in Edge.

The Allow localhost loopback setting in about:flags is enabled by default, but I have unchecked with it disabled too. Disabling the setting causes all URLs to stop working in Edge regardless of zone as expected. I have installed all updates including the Anniversary update.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Christian F.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To to “Dave B.”

      Changed Assigned To from “Dave B.” to “Forbes H.”

      Changed Status to “Confirmed”

    • I have the same problem with accessing a VM on a local virtual switch via Edge (the address is 192.168.78.132:2378) and no issues when using Chrome, so not a firewall problem.

      I’ve tried the about:flag option and running CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe but neither helps.

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

    Sign in