Improve TransportSecurityState data storage.

chrome/browser/net/chrome_fraudulent_certificate_reporter.cc

Index: chrome/browser/net/chrome_fraudulent_certificate_reporter.cc
===================================================================
--- chrome/browser/net/chrome_fraudulent_certificate_reporter.cc	(revision 186438)
+++ chrome/browser/net/chrome_fraudulent_certificate_reporter.cc	(working copy)
@@ -65,14 +65,9 @@
 
 void ChromeFraudulentCertificateReporter::SendReport(
     const std::string& hostname,
-    const net::SSLInfo& ssl_info,
-    bool sni_available) {
+    const net::SSLInfo& ssl_info) {
   // We do silent/automatic reporting ONLY for Google properties. For other
   // domains (when we start supporting that), we will ask for user permission.

[palmer, 2013/03/25 23:54:34]

So what code now enforces this comment?

I think we need to keep the IsGooglePinnedProperty check up here in
chrome/browser code, because at some point we're going to fire off UI to ask the
user if they want to report more kinds of pinning failure, and we can't do that
in e.g. the net/ layer.

[unsafe, 2013/03/26 01:42:22]

URLRequestHttpJob::OnStartCompleted().  
The reason for here is that IsGooglePinnedProperty() was moved into DomainState,
so that all relevant preloaded state gets loaded via
TSS::GetPreloadDomainState(), instead of needing a different function for
searching preload entries.

The URLRequestHttpJob function already deals with a TSS instance for
ShouldSSLErrorsBeFatal(), so it seemed easier to handle the check at that level,
instead of pushing sni_available down to here, then figuring some way to get at
the TSS object from here...

But I could move the check back to here, if there's some way to get at a TSS
object?

-  if (!net::TransportSecurityState::IsGooglePinnedProperty(hostname,
-                                                           sni_available)) {
-    return;
-  }
 
   std::string report = BuildReport(hostname, ssl_info);