Nathan, can you take a look at this bug? Looks like the policy to prevent clicking through interstitals might not be working as expected.

The interstitial code looks at pref "safebrowsing.proceed_anyway_disabled." Julian, can you point us to the code that is supposed to set that from policy DisableSafeBrowsingProceedAnyway? I'm not familiar with that part.

--> carlosil, owner of interstitials

The pref is mapped to the policy correctly and works but the problem is that it only covers Safe Browsing interstitials like Phishing sites e.g. the ones listed here https://testsafebrowsing.appspot.com/ but not SSL related interstitials like the ones at https://badssl.com. 

I guess the solution would be to either document the limitations of this policy or if possible expand its scope to SSL related errors as well.

This feels like it's working as intended since the policy is explicitly named "SafeBrowsing". My (uneducated) guess is that covering SSL on the same policy might not be desirable (e.g. you might want to prevent users clicking through SB since those are almost certainly bad sites, but you might have some broken/misconfigured enterprise tool that requires them to click through an SSL warning). I'd say a separate policy for blocking SSL clickthroughs would be better if we want to offer that choice.

emilyschechter -- Any thoughts Julian's comment #4?