Custom CA in headless Chrome on Linux

[ad...@rigo.sk]

To test my website locally I created a custom CA and the CA is added to the ~/.pki/nssdb.
I'm trying to use Chrome headless with NO --no-certificate-errors 

I get ERR_INSECURE_RESPONSE error upon navigating to the webpage, while Chrome without the --headless flag accepts the custom CA signed SSL cert as a valid cert and it can open the webpage.

Do I miss something? Should I file a bug?

I'm aware that --no-certificate-errors won't work, however I'm able to run the local version without the --headless and --no-certificate-errors flags. I didn't find any issues related to the usage of the CA store while running with --headless

Best regards,

Adam Lippai

[Sami Kyostila]

Hi Adam,

Sounds like this should work. Would you mind filing a bug at crbug.com?

- Sami

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/f926f8e4-7e96-431a-aa17-3bc8ad4fef9b%40chromium.org.

[ad...@rigo.sk]

Sure!

https://bugs.chromium.org/p/chromium/issues/detail?id=765305

Best regards,

Adam Lippai

[fmi...@gmail.com]

Hi. In Windows 10 I have found a similar issue just when running headless Chrome in Session 0 (from a Windows Service). If I run headless Chrome from another Session, then it recognizes the custom CA ok. The only problem is that I do not get it to log ERR_INSECURE_RESPONSE, just the white blank page response. I've tested it using a real CA, and it works ok.