How Firefox Got Fast Again

Re:How Firefox Got Fast Again by SomeHacker44 on Monday November 13, 2017 @04:36PM (#15690483)

The most anti-user "User Agent" thing of Chrome, in my experience, is their refusal to let me open my myriad dev sites with bogus certificates claiming some bullshit HSTS problem, without giving me a "do it anyway, you stupid browser" button.

So, literally, I still use Chrome (because I'm too used to it), but I do all my dev work on Firefox, which has a dev-friendly user policy.

[ Parent | on HN ]

Re:How Firefox Got Fast Again by Retr0spectrum on Monday November 13, 2017 @04:39PM (#15690512)

I believe if you type "badidea" at the error page it will let you through unconditionally.

[ Parent | on HN ]

Re:How Firefox Got Fast Again by SomeHacker44 on Monday November 13, 2017 @05:06PM (#15690716)

Holy crap. I have Google'd a zillion times for a workaround and they all were insane "do about a zillion steps on Keychain access or just fix your server." THANK YOU BOTH.

[ Parent | on HN ]

Re:How Firefox Got Fast Again by pzduniak on Monday November 13, 2017 @05:06PM (#15690710)

I wish I knew that when adding auto-HTTPS and HSTS functionality to a product - typing out "chrome://net-internals/#hsts" almost became muscle memory.

[ Parent | on HN ]

Re:How Firefox Got Fast Again by gkfasdfasdf on Monday November 13, 2017 @04:44PM (#15690547)

FWIW blocking sites with bogus certs and not allowing a user bypass is exactly what the HSTS RFC requires. If you were testing the HSTS feature of your website, Chrome is doing the right thing. It's possible to clear Chrome's cache of HSTS-enabled sites btw: https://www.thesslstore.com/blog/clear-hsts-settings-chrome-...

[ Parent | on HN ]

Re:How Firefox Got Fast Again by dylz on Monday November 13, 2017 @04:38PM (#15690507)

type badidea

[ Parent | on HN ]