5 ms·
I've found the exact opposite to be true in my very specific experience. Five years ago I used every Google product under the sun, today the only Google product
by freehunter 6y ago
I've found the exact opposite to be true in my very specific experience. Five years ago I used every Google product under the sun, today the only Google product I use at all (even search) is Chrome because it's the only one I haven't been able to replace.
I try Firefox with a fresh install on nearly every major release and I keep it installed as a secondary browser, but I can never manage to use it as my daily browser. For whatever reason, none of my company's (major tech company but not a competitor to Mozilla in any way) internal web pages load in Firefox. No error, no warning, nothing in the console, just zero content. Blank page. I've tried it on two computers with the same result and just nothing. No extensions installed, nothing I've installed on my network or computer to block anything. It just doesn't load anything.
On the other hand I keep Firefox installed because Chrome refuses to load my dev environment with a self-signed certificate. Firefox will let me click "I accept the risk" but Chrome just refuses to load with a self-signed cert.
I'd love to use just one (preferably Firefox) but I guess the web is still hard to get right.
- bzb3 6y agoYou can bypass the Chrome dialog by typing "thisisunsafe" in the error page.
- freehunter 6y agoThat's a stupidly hidden way to go about it.
- dylz 6y agoIIRC, the intent is that no one should be doing this and anyone doing it should be at least technical enough to figure out what they're doing and be reminded that it's a bad idea.
- freehunter 6y agoAnd 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...
- Wowfunhappy 6y agoYeah, I actually think these sorts of strategies are clever. They're a way to protect normal users without outright barring power users from doing as they wish. macOS operates in a similar way. I really like how the difficulty increases depending on the task: • Want to allow one app through Gatekeeper? Instead of double-clicking the app icon directly, right click it and select "open". • Want to turn off Gatekeeper for all apps? You need to open the Terminal and execute a command. • Want to turn off System Integrity Protection? You need to reboot your computer into recovery mode and execute a Terminal command there.
- lostcolony 6y agoExcept for those of us who are finding out about it only via a Hacker News comment. As happened with this user, who seems, you know, sufficiently a power user to need that info. Even a "if you know this site to be safe, please read this knowledge base article (link)" and buried in that, amidst all the reasons you shouldn't use untrusted certs, are the instructions.
- londons_explore 6y agoIf you keep up to date with commits on the chromium code repo, you'd see them change it from time to time. For a while it was 'youshallnotpass'. You probably shouldn't be using an opensource project without at least a cursory glance at the code anyway, especially as a power user.
- lostcolony 6y agoYou're kidding right? You look at every commit of every open source app you use, or that a closed source app is built atop? For me, off the top of my head, that would mean, yes, Chrome, Firefox, the Linux Kernel, Libre Office, Android, VLC...probably plenty more that I am unaware are open source, and that's not even considering the dev tools to do my job. When would I actually have time to have a life?
- skykooler 6y ago
- jschwartzi 6y agoOn the other hand these stupid dialog tricks are why I stopped using Chrome. I'm not an idiot and I know what I'm doing. It's pretty arrogant to assume that I shouldn't be visiting my router's configuration page just because it uses a self-signed certificate. I don't care to set up an X.509 infrastructure at my house, thank you. Please stop mollycoddling me. Firefox continues to do a good job of just letting me visit the damn website after warning me.
- dylz 6y agoI'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 ago
- tracker1 6y agoReminds me of the default admin password for an app I've worked on... "You should change me."
- dewey 6y ago> No error, no warning, nothing in the console, just zero content. Blank page. Have you tried disabling the tracking protection, maybe it's mistakenly blocking some JS?
- heavyset_go 6y agoTry sending your company's internal sites a Chrome User-Agent from Firefox. There are extensions that let you do this.
- brigandish 6y agoI was doing that but it does break things so you need to remember you're doing it. For weeks I wondered why Slack wouldn't work via my browser until I found it was loading some Javascript only when UA was set to Chrome, and that was breaking something.
- Bedon292 6y agoAssuming you are on a Windows domain, since they are able to control your Chrome. Chrome uses all the built in Windows settings. Have you check for proxy settings in internet options? Firefox I believe still uses standalone settings, and will need to be configured manually. Other thing they could be doing is adding certificates to the Windows certificate store, that Firefox does not trust. Though I expect you would see an error about invalid certs in that case.
- acomjean 6y agoWhen I worked at a company Firefox worked then didn’t. I think the web proxy needed to use the company installed cert or some such weirdness: https://security.stackexchange.com/questions/133254/how-does-ssl-proxy-server-in-company-work https://security.stackexchange.com/questions/133254/how-does...
- StavrosK 6y agoWouldn't the fact that your company's site doesn't work on Firefox need to be filed as a bug on your site's bug tracker?
- freehunter 6y agoYou’re assuming I have access to my huge mega tech company’s website’s bug tracker. I do not.