Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
INSECURE error not working as expected
See original GitHub issuelighthouse https://zach.diemer.codes/
This should return an LHR with a runtimeError set to the INSECURE_DO CUMENT_REQUEST
Instead:
- we first wait for Page.navigate to timeout. (kind of a bummer…)
- the timeout of Page.navigate triggers a rejection which is unhandled
- it bails completely instead of making an LHR
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Fix the HTTPS Not Secure Error - Seer Interactive
Once the crawl is complete, click “Reports” in the top ribbon, then “Insecure Content”.
Read more >code-server is being accessed over an insecure domain. Web ...
Your browser has not given code-server access to certain features. Web views, the clipboard, and other functionality will not work as expected.
Read more >A Simple Explanation of SSL Certificate Errors & How to Fix ...
Learn what an SSL certificate error is. Then walk through various steps you can take to fix the error and get your site...
Read more >docker --insecure-registry flag not working as expected
Set the following flag in the daemon.json file: { "insecure-registries": ["registry:8443"] } · Restart Docker $ sudo systemctl restart docker.
Read more >wattsupwiththat.com is throwing an 'insecure' error. I trust them ...
The error shown is: Your connection is not secure. "The owner of wattsupwiththat.com has configured their website improperly.
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 Free
Top 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
I forgot @exterkamp bailed on that in #6671 😦
Looks like just throwing the error when the security issue is first found will be OK now that Shane fixed LR’s error handling in #6739. groovy