I wonder why this was added in the first place. This error may triggered in an overly-broad manner. Can we check different errors that are returned with https://www.badssl.com/ to ensure this doesn't remove the interstitial for any hosts that are valid?

For testing, I've typically just done curl -O badssl.html https://www.badssl.com/ and replaced all the HTTPS links with HTTP within the HTML. This is necessary since direct links to HTTPS pages do not trigger the interstitial, and it's easier than copy/pasting the URL and removing the 's' each time.

I wonder why this was added in the first place. This error may triggered in an overly-broad manner. Can we check different errors that are returned with https://www.badssl.com/ to ensure this doesn't remove the interstitial for any hosts that are valid?

For testing, I've typically just done curl -O badssl.html https://www.badssl.com/ and replaced all the HTTPS links with HTTP within the HTML. This is necessary since direct links to HTTPS pages do not trigger the interstitial, and it's easier than copy/pasting the URL and removing the 's' each time.

I will check that out as well to make sure this doesn't hit other cases. I truly hope "unknown hosts" doesn't mean something else :(

I wonder why this was added in the first place. This error may triggered in an overly-broad manner. Can we check different errors that are returned with https://www.badssl.com/ to ensure this doesn't remove the interstitial for any hosts that are valid?
For testing, I've typically just done curl -O badssl.html https://www.badssl.com/ and replaced all the HTTPS links with HTTP within the HTML. This is necessary since direct links to HTTPS pages do not trigger the interstitial, and it's easier than copy/pasting the URL and removing the 's' each time.

I will check that out as well to make sure this doesn't hit other cases. I truly hope "unknown hosts" doesn't mean something else :(

@Hainish I went through badssl.com and have not seen "NS_ERROR_UNKNOWN_HOST" occur for other SSL errors. I did see ""NS_ERROR_CONNECTION_REFUSED"" occur sometimes for non existent sites. Maybe this is where the murky issues lied out with these errors? Maybe that jogs a memory?

@Hainish I went through badssl.com and have not seen "NS_ERROR_UNKNOWN_HOST" occur for other SSL errors. I did see ""NS_ERROR_CONNECTION_REFUSED"" occur sometimes for non existent sites. Maybe this is where the murky issues lied out with these errors? Maybe that jogs a memory?

Well, that works for me then. Thanks for looking into it, let's merge.