Doesn't detect that page doesn't load due to bad SSL interstitial
See original GitHub issueMaybe this is a bit contrived. But I ran a lighthouse review
lighthouse https://www.cnn.com
Which times out because the library doesn’t detect that the insecure content warning is set. Similarly:
lighthouse https://www.some-none-existing-domain.com
Which happily reviews the chrome error page. Shouldn’t the library detect these errors and show a userfriendly message?
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
119252 - SSL interstitial error "proceed anyway" / "back to ...
I re-opened the last tab that was closed (some non-ssl wikipedia page) and tried navigating to a different ssl page in A to...
Read more >Failed to load resources when accessing remote HTTPS ...
I tried this and after proceeding through the certificate error interstitial it all seemed to work; no resource load failures in the console...
Read more >weblayer/browser/ssl_browsertest.cc - chromium/src - Git at Google
Now verify that the interstitial is in fact an SSL interstitial. ... login URL, so simply detect the start of the navigation to...
Read more >How to Fix the NET::ERR_CERT_AUTHORITY_INVALID Error
Even if you do have an SSL certificate installed on your website, ... Simply put, your browser doesn't recognize the validity of your ......
Read more >When you use 'badidea' or 'thisisunsafe' to bypass a Chrome ...
You should find out why the site is showing the error and/or stop using it until they fix it. HSTS specifically adds protections...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Talking about this page: Another option for me would be starting Chrome with a switch that disables this page, if such switch exists.
As far as I can see, request events just stop coming in. No failed request event.
Thanks for the details on this. I’m folding it into #2784