Stop revoking cert exceptions on resources loaded from cache

content/browser/ssl/ssl_manager.cc

Index: content/browser/ssl/ssl_manager.cc
diff --git a/content/browser/ssl/ssl_manager.cc b/content/browser/ssl/ssl_manager.cc
index 4526ab3d13e622ed6a6437f776e42ec9eb153273..204e9ed629b2b1b3dd1aaab1cda35c7b11ba1fef 100644
--- a/content/browser/ssl/ssl_manager.cc
+++ b/content/browser/ssl/ssl_manager.cc
@@ -19,7 +19,6 @@
 #include "content/common/ssl_status_serialization.h"
 #include "content/public/browser/browser_context.h"
 #include "content/public/browser/browser_thread.h"
-#include "content/public/browser/load_from_memory_cache_details.h"
 #include "content/public/browser/navigation_details.h"
 #include "content/public/browser/resource_request_details.h"
 #include "content/public/common/ssl_status.h"
@@ -140,12 +139,6 @@ void SSLManager::DidRunInsecureContent(const GURL& security_origin) {
   UpdateEntry(navigation_entry);
 }
 
-void SSLManager::DidLoadFromMemoryCache(
-    const LoadFromMemoryCacheDetails& details) {
-  // Simulate loading this resource through the usual path.

[jww, 2016/08/09 02:42:18]

nit: Probably should update the comment ssl_policy.cc at
https://cs.chromium.org/chromium/src/content/browser/ssl/ssl_policy.cc?sq=pac...
to state that the subresource case is purposefully ignored (and why).

[felt, 2016/08/10 14:17:17]

Done.

-  policy()->OnRequestStarted(details.url, details.cert_id, details.cert_status);
-}
-
 void SSLManager::DidStartResourceResponse(
     const ResourceRequestDetails& details) {
   // Notify our policy that we started a resource request.  Ideally, the