For HSTS, it’s based on the spec. There’s not supposed to be a user-accessible o...

epmatsw on Feb 9, 2018 | parent | context | favorite | on: Chrome 68 will mark all HTTP sites as “not secure”

For HSTS, it’s based on the spec. There’s not supposed to be a user-accessible override for HSTS errors, which is why Chrome hides it behind that easter egg. Firefox has no override of any kind.