setting to allow self signed certs
Reported by
bhargav....@gmail.com,
Oct 5 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Got the website https://www.pcwebshop.co.uk/ 2. 3. What is the expected behavior? Certificate warning What went wrong? Setting that will also to by pass this warning and directly go the web page Did this work before? No Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.12.6 Flash Version: Shockwave Flash 27.0 r0 I understand there is a security risk with this setting but it would be very useful for a developer. May be it can be added to developer tools. Accepting certificate with each docker container is very annoying for a a developer
,
Oct 5 2017
This is working as intended. After you accept an invalid certificate, that acceptance is cached by Chrome for one week (Issue 487270). If you routinely use a self-signed certificate, you can configure your operating system's trust store to trust it, at which point Chrome will no longer show a warning. In this particular case, the problem with the certificate isn't that it's self-signed, but instead that it is a certificate for a different hostname. If you do not want to access the site with the hostname matching the certificate, and do not want to (or cannot) change the certificate to refer to the correct hostname, you could use the --ignore-certificate-errors-spki-list command line flag to tell Chrome to ignore certificate errors for the specific certificate. |
||
►
Sign in to add a comment |
||
Comment 1 by bhargav....@gmail.com
, Oct 5 2017