Issue metadata
Sign in to add a comment
|
Chrome headless screenshot hangs on SSL error |
||||||||||||||||||||||
Issue descriptionChrome 60.0.3086.0 OSX 10.12.4 What steps will reproduce the problem? (1) Run --headless --screenshot "https://expired.badssl.com" What is the expected result? Chrome finishes running, and outputs an error or a screnshot of the SSL interstitial What happens instead? Chrome hangs. I'm guessing this is due to Issue 392354. I've only tested on Mac, but I presume this affects other platforms, too.
,
May 2 2017
eva.aillaud84@: Your comment does not seem relevant to this bug. Did you meant to comment somewhere else?
,
May 6 2017
eseckler, could you please take a look?
,
May 8 2017
Yeah, --screenshot doesn't work with sites containing ssl errors. If you'd like to access (and take screenshots of) sites with ssl errors, you can use --remote-debugging-port=xxxx with your own DevTools client and the DevTools commands for certificate error handling. See https://crbug.com/659662 .
,
May 8 2017
I personally don't need to. But what about people writing scripts that expect Chrome not to hang?
,
May 9 2017
Maybe we should detect such situations and abort in headless_shell. Note that the non-remote-debugging-port functionality of headless_shell is an example for how to use DevTools in headless mode. It's not really intended to be relied upon for correctness.
,
May 9 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted