Steps to reproduce
Edge is unable to retrieve webpage at a single URL. Web host at the URL was configured to use 301 permanent redirect for HTTP to HTTPS, then on HTTPS, depending on the host name in the header, redirect to different ports on the same machine. e.g. HTTP://host1.example.com - 301 redirect -> HTTPS://host1.example.com - 302 redirect --> HTTPS://host1.example.com:8443 The URL is a locally hosted, private website. Edge works normally for all other URLs.
When problem URL is entered in address bar, edge ignores the URL and stays on the previous webpage, restoring the address bar to previous webpage URL. No error page is displayed. Going directly to the final URL (HTTPS://host1.example.com:8443) also results in the same behavior. Substituting IP address for domain name results in the same behavior.
Using firefox on the same machine with the same URL results in firefox showing the webpage at HTTPS://host1.example.com:8443. I believe this rules out network and/or web host issues.
Internet Explorer 11 loads the webpage at the URL with no problems.
I have reset Edge with no change. I have reinstalled Edge with no change. I have used a second login account and Edge will still not load the intended webpage.
I installed Fiddler 4 and now Edge is able to reach the intended webpage only when Fiddler 4 is running. My understanding is that Fiddler 4 acts as a local proxy so whatever in Edge that’s blocking the URL is bypassed when the HTTPS session is proxied through Fiddler.
How do I reset Edge such that this URL is no longer blocked?
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Zachariah L.”
Thanks for contacting us in regards to this issue. Based on the information you provided me, I was unable to replicate this problem. In order to help me identify this as an Edge issue, could please provide me with a code snippet or example project that I can run to reproduce this issue?
If you are using a self-signed certificate for the HTTPS server then perhaps that could be causing some issues with Edge. Here is some Microsoft documentation that might help sort out potential certificate problems:
Creation via PowerShell: https://technet.microsoft.com/itpro/powershell/windows/pkiclient/new-selfsignedcertificate
Installing Certificates with Microsoft Management Console (MMC): https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in
At this time I will close out this issue. If you are still able to reproduce this issue then please provide the details I requested and I will resume investigating this issue.
The Microsoft Edge Team.
- Microsoft Edge Team
Changed Status to “Not reproducible”