Remember user decisions on invalid certificates behind a flag

android_webview/browser/aw_browser_context.cc

Index: android_webview/browser/aw_browser_context.cc
diff --git a/android_webview/browser/aw_browser_context.cc b/android_webview/browser/aw_browser_context.cc
index 4287b02514445696ed74f8dba84bf9ef92daf4de..842eedcba962f2b90d2d7dc90301be3b0f397b48 100644
--- a/android_webview/browser/aw_browser_context.cc
+++ b/android_webview/browser/aw_browser_context.cc
@@ -274,6 +274,12 @@ content::PushMessagingService* AwBrowserContext::GetPushMessagingService() {
   return NULL;
 }
 
+content::SSLHostStateDecisions* GetSSLHostStateDecisions() {
+  // TODO(jww): For now, do not support any certificate memory for WebView, but
+  // this probably needs to change.

[Ryan Sleevi, 2014/07/17 23:19:35]

I doubt it. WebView makes such responsibility the callers, IIRC.

[jww, 2014/07/21 23:39:32]

Done.

+  return NULL;
+}
+
 void AwBrowserContext::RebuildTable(
     const scoped_refptr<URLEnumerator>& enumerator) {
   // Android WebView rebuilds from WebChromeClient.getVisitedHistory. The client