title: Microsoft Edge forcing HTTPS and refusing a self-signed certificate
body: <p>Doing dev work on several sites on my local (Windows 10) PC when out of the blue this morning one site refuses to load in Microsoft Edge (Version 89.0.774.45 (Official build) (64-bit)).  Other local sites are working fine.</p>
  <p>I removed the redirect to SSL from web.config and issued a fresh self-signed certificate:  NET::ERR_CERT_COMMON_NAME_INVALID - You can't visit local-prodject.mydomain.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.</p>
  <p>There is no HSTS in web.config.  I removed the HTTPS redirect from web.config and it's still trying to force HTTPS.  I've done the edge://net-internals/#hsts to delete for local-prodject.mydomain.com and localhost, no change.</p>
  <p>I'd prefer to have self-signed working as it was yesterday, and on other sites on my local PC so when they get pushed to a production environment they're ready to go.</p>
  <p>I should also note that Chrome and Firefox (Dev and regular) work fine.</p>