3 ms·
And instead many people will just do a Google search for "Chrome [insert error here]" and run the first command they find, while people like me will say "okay I
by freehunter 6y ago
And instead many people will just do a Google search for "Chrome [insert error here]" and run the first command they find, while people like me will say "okay I'll just Firefox where I can click past this warning".
- dylz 6y agoFor what it's worth I've always been able to click straight through a self-signed cert on Chrome - in fact I just did it right now to log in to something internal. I am a nearly 50-50 split Firefox/Chrome user. Are you sure you aren't sending HSTS headers that demand the site be TLS in some way? Also, have you considered the slightly-saner way of doing it, which is making an internal self-signed CA, trusting that internal CA, and then having it sign the rest of your "self dev stuff" certs?
- freehunter 6y agoIf it was HSTS it wouldn't load in Firefox, would it?
- dylz 6y agoIf it was HSTS it would not load in both, with no button to bypass. If it was not HSTS you can click through a non-obvious button in both.
- freehunter 6y agoWell Chrome has no button and Firefox has a button, so...