Issue metadata
Sign in to add a comment
|
--dump-dom doesn't seem to work with --ignore-certificate-errors
Reported by
potoms....@gmail.com,
Jan 5 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. run chrome with the following arguments: /Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --ignore-certificate-errors --dump-dom https://wrong.host.badssl.com 2. wait What is the expected behavior? The dom gets printed on the screen like with a normal website What went wrong? nothing happens Did this work before? N/A Chrome version: 57.0.2972.0 Channel: canary OS Version: OS X 10.12.2 Flash Version: Shockwave Flash 24.0 r0
,
Jan 6 2017
Tested on Mac OS 10.12.2 using chrome canary M57 #57.0.2973.0 and followed the below steps: Steps tried to reproduce: 1. Opened chrome via command prompt using command "/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --ignore-certificate-errors --dump-dom https://wrong.host.badssl.com". 2. Message is displayed in the page. Attached screenshot for reference. @potoms.jan-- Could you please check the attached screenshot and confirm us if we had followed the correct process or not ...and also provide us the expected result screenshot , for easy investigation. Thanks!
,
Jan 6 2017
I'm sorry, I mixed up a bit. I'm trying out --headless mode in the latest Chromium on linux running with: --headless --no-sandbox --disable-gpu --ignore-certificate-errors --dump-dom https://badssl.com works running with: --headless --no-sandbox --disable-gpu --ignore-certificate-errors --dump-dom https://wrong.host.badssl.com hangs
,
Jan 9 2017
cc-ing some headless folks and adding our project label :) We might not be handling --ignore-certificate-errors in headless correctly.
,
Jan 10 2017
,
May 15 2017
,
Jul 19 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Jan 6 2017