Skip to content
This repository was archived by the owner on Jun 14, 2024. It is now read-only.
This repository was archived by the owner on Jun 14, 2024. It is now read-only.

How to allow access when developing with Let's Encrypt #695

Open
@siegfried01

Description

@siegfried01

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions