3 ms·
I'm confused - Firefox and Chrome act completely identically to a self signed cert for me. Both let me click through after looking at the cert or expanding a se
by dylz 6y ago
I'm confused - Firefox and Chrome act completely identically to a self signed cert for me. Both let me click through after looking at the cert or expanding a section. I have never been "blocked" by some hidden modal unless the site chooses to be HSTS-enforcing, and in that case Firefox does not allow a clickthrough either.
Both examples on latest current, taken right now:
Firefox: https://i.imgur.com/4VMjDZ4.png https://i.imgur.com/4VMjDZ4.png
Chrome: https://i.imgur.com/YosvXEu.png https://i.imgur.com/YosvXEu.png
For HSTS, both Firefox and Chrome act identically and do not allow clickthrough: https://i.imgur.com/WPCTep1.png https://i.imgur.com/WPCTep1.png
- maest 6y agoYoure confused because you're not using Chrome on OSX: on osx there's no "Proceed to <website>" option.
- gowld 6y agohttps://support.google.com/chrome/thread/23226743?hl=en https://support.google.com/chrome/thread/23226743?hl=en
- dylz 6y agoI'm now even more confused: https://i.imgur.com/jl9agwG.png https://i.imgur.com/jl9agwG.png
- freehunter 6y agoYou’re right to be confused because I’ve never seen a rhyme or reason to it either. I generated a cert using OpenSSL’s command line tools and told Django’s manage.py to use my self-generated cert and it works in Firefox but not Chrome. It did work in Chrome. And then after an update it didn’t work anymore. I don’t know why and it seems like no one else here does either.
- jschwartzi 6y agoI was literally going to say that at one point that screen didn't look like that, and it appears it still doesn't but only sometimes.