3 ms·
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 bul
by SomeHacker44 9y ago
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.
- dylz 9y agotype badidea
- Retr0spectrum 9y agoI believe if you type "badidea" at the error page it will let you through unconditionally.
- pzduniak 9y agoI wish I knew that when adding auto-HTTPS and HSTS functionality to a product - typing out "chrome://net-internals/#hsts" almost became muscle memory.
- SomeHacker44 9y agoHoly 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.
- gkfasdfasdf 9y agoFWIW 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-firefox/ https://www.thesslstore.com/blog/clear-hsts-settings-chrome-...