Ignoring certificate errors in the headless browser

[jala...@gmail.com]

What is the best approach to ignoring certificate errors in the browsers. I am hitting a site with a wildcard certificate and the headless browser is returning INSECURE_RESPONSE

 profile.detail {"requestId":"208.7","timestamp":72093.762846,"type":"Document","errorText":"net::ERR_INSECURE_RESPONSE","canceled":false,"eventType":"loadingFailed","timeInMs":1499186059391} +10ms

 

Is there any way to ignore this error?

cheers

</jima>

[Boris Okunskiy]

Yes, just run Chrome with --ignore-certificate-errors

[jala...@gmail.com]

Tried that but it doesn't seem to work

[headless-man]

try with protocol, here's the example

[jala...@gmail.com]

perfect ... worked like a charm

[Sami Kyostila]

I'm not quite sure which problem you're running into with chrome-remote-interface, but I suggest starting with the basic example here: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md#usage-from-node_js

- Sami

pe 20. lokak. 2017 klo 5.11 chrome-guy <sou...@cushion.ai> kirjoitti:

Can someone please share some example code of how to set up the chrome-remote-interface code? Running into an issue with using that because of a problem with chrome hanging & not being able to connect to the remote-debugger-port (this reported bug). How were you able to work around that bug to get chrome-remote-interface to connect?

--
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/7dd7787d-24d0-40cc-ae22-8d037957cc8f%40chromium.org.