Hacker News new | ask | show | jobs
by triplenineteen 2984 days ago
Sorta. In most browsers you can manually delete the HSTS property on a per-domain basis. Presumably, anyone doing this knows the risks.
1 comments
caymanjim 2984 days ago
In Chrome, it's a real pain in the ass, and it's buried deeply. It's not available at all in the settings UI (not even in advanced settings).
link
ascorbic 2984 days ago
You can type "badidea" at the warning page to skip it.
link
rocqua 2984 days ago
Changed to "This is unsafe" (followed by enter) in chrome 65. Try it at https://badssl.finn.io/
link
Moter8 2984 days ago
Doesn't work for me (anymore) in Chrome 65. Used to work.
link
CydeWeys 2984 days ago
I think it was changed to something like "thisisunsafe" now.
link
rocqua 2984 days ago
Just checked this on chrome 65 on https://badssl.finn.io/ seems to work (also need to press enter).
link
verbify 2984 days ago
That's correct, tested it with https://badssl.finn.io/
link
ZeroCool2u 2984 days ago
Had no idea about that 'badidea' work around in chrome. Just tried it and it actually worked.
link
hkdobrev 2984 days ago
In Chrome, clearing the cache, clears the saved HSTS records which are not preloaded in the browser.
link