404 Accessing Visual Studio Project "localhost" Root When Edge Appends "index.html"

Question

I'm positive at this point that this is a Microsoft Edge issue because Chrome and Firefox do not do this. When I run a Visual Studio ASP.NET project locally and attempt to access the root of the site (e.g., https://localhost:5001), I consistently receive a 404 (Not Found) error from Microsoft Edge because it forces a change to the URL in the address bar to "https://localhost:5001/index.html"

Chrome and Firefox do not do this. Both of these browsers honor the controller routing in my application and load the content from my action method exactly how I would expect. This only happens in Edge.

If, in Edge, I edit the address bar and remove "index.html" from the URL the browser will force "index.html" back into the URL as soon as I press Enter. This is consistent, reproducible behavior and it's wrong. I've looked in settings for the browser and can find nothing related to this behavior. I've searched the Internet for similar questions and I don't see any. I'm at my wits' end because this has cost me multiple hours of troubleshooting my ASP.NET code, only to find out that it's a problem with this browser alone.

What is happening in this scenario? Why is Edge doing this and how can I make it stop?

My Visual Studio 2019 project is an ASP.NET Core 3.1 Web Application with a single controller (with ApiControllerAttribute and derived from ControllerBase). My browser is version 86.0.622.51 (Official build) (64-bit).

Answer 1

Hi,

Thank you for writing to Microsoft Community Forums.

We understand the concern as you are getting 404 error while running a Visual Studio ASP.NET project locally and attempt to access the root of the site.

However, for a better clarity on your concern, I would suggest you to post your query in TechCommunityforums, where we have experts and support professionals who are well equipped with the knowledge on Edge feature to assist you with the appropriate troubleshooting steps.

Regards,

Let us know the results. If the issue persists, we will certainly assist you further.

Aditya Roy

Microsoft Community – Moderator