Reputation: 655
Last week I could navigate to edge://flags/#allow-insecure-localhost
and I could edit the flag so that my localhost could serve invalid SSL certificates. Today after the latest Edge update (Version 88.0.705.50) I can no longer find this flag.
Has it moved to another secret area? How can I allow insecure localhost SSL certs again for my application?
Upvotes: 18
Views: 33825
Reputation: 706
For me, this setting resolves the issue. Under edge://flags/
, it should be enabled.
Upvotes: -1
Reputation: 3643
to workaround this issue on version 119:
Temporarily unexpire M118 flags
and enable it, the browser will ask you to restart after that.#allow-insecure-localhost
flag appear again. Enable it and enjoy happy developer's life.Upvotes: 7
Reputation: 71
The current stable version of Chromium v119.0
doesn't have this flag.
It's because the expiration version for this flag is modified from 118.0
to 130.0
on Oct 4, 2023 and this change would be released in v120.0
(reference)
As of now, v120.0
is scheduled to be in stable channel on Dec 5, 2023
. (reference). It might take a bit longer if you are using microsoft edge.
Upvotes: 4
Reputation: 366
I had the same issue but was able to fix it with the 'WebTransport Developer Mode' flag
Upvotes: -3
Reputation: 12946
This seems to be an issue with Edge 88.0.705.50. In higher version, Edge 89.0.767.0, the flag comes back again:
I think the issue will be fixed in future version of Edge Stable. You can wait for the updates and download Edge Dev to test your app as a workaround for now.
Upvotes: 15