How to allow access when developing with Let's Encrypt

Open siegfried01 opened this issue 5 years ago • 1 comments

It seems there has been a change in the behavior of Edge with regard to unsafe content...

I'm deploying this sample program to Azure kubenetes https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/blob/master/4-WebApp-your-API/4-2-B2C/README.md

I'm using the non-production version of lets encrypt (unsigned certificates) as https://docs.microsoft.com/en-us/azure/aks/ingress-static-ip which should cause warning messages... It used to be (Nov 2020) that edge would let me proceed to the unsafe site.

But these days, even when I go to the edge settings and allow unsafe content for my site, edge (unlike firefox) won't let me proceed.

How can I use edge to debug my site until I'm ready to get real certificates for my web site?

Thanks

Siegfried

Jan 08 '21 03:01 siegfried01

https://github.com/MicrosoftEdge/Status#status-

This project contains the data for status.microsoftedge.com, a portal for the latest implementation status and future roadmap for interoperable web platform features in Microsoft Edge and other browsers, including Internet Explorer.

I think this is a question for StackOverflow

Jan 08 '21 03:01 nschonni