Is the --ignore-certificate-errors flag getting ignored a new thing? I can remember it working before.
Anyway, is there any way to circumvent it short of running a Node HTTP proxy inside the extension? My use case is navigating to an untrusted page (it's a https://<ip> so a valid certificate is impossible).
Is the
--ignore-certificate-errorsflag getting ignored a new thing? I can remember it working before.Anyway, is there any way to circumvent it short of running a Node HTTP proxy inside the extension? My use case is navigating to an untrusted page (it's a
https://<ip>so a valid certificate is impossible).