Check Expect-CT at connection setup

chrome/browser/ssl/chrome_expect_ct_reporter.h

Index: chrome/browser/ssl/chrome_expect_ct_reporter.h
diff --git a/chrome/browser/ssl/chrome_expect_ct_reporter.h b/chrome/browser/ssl/chrome_expect_ct_reporter.h
index 28ac4aa29eeff78f53e433767c2bd3fe55253f85..27edf2c6511085e96d71b73ac60c76d0234b757b 100644
--- a/chrome/browser/ssl/chrome_expect_ct_reporter.h
+++ b/chrome/browser/ssl/chrome_expect_ct_reporter.h
@@ -28,7 +28,10 @@ class ChromeExpectCTReporter
   // net::ExpectCTReporter:
   void OnExpectCTFailed(const net::HostPortPair& host_port_pair,
                         const GURL& report_uri,
-                        const net::SSLInfo& ssl_info) override;

[estark, 2017/05/01 23:14:18]

Two notes:
- I changed this argument from an SSLInfo to take the individual things that are
needed from the SSLInfo, because this method is now called from
ShouldRequireCT() callsites which don't all have a full SSLInfo available yet.
- It's currently odd that this reporting code is implemented in //chrome. (It's
a vestige from the experimental preload-list-only version of Expect-CT, for
which it seemed more reasonable to confine reporting to //chrome because it was
a Chrome-only experiment.) Now that Expect-CT is being standardized in the
platform, I'll move this code to either //content or //net in a follow-up CL.

+                        const net::X509Certificate* served_certificate_chain,
+                        const net::X509Certificate* validated_certificate_chain,
+                        const net::SignedCertificateTimestampAndStatusList&
+                            signed_certificate_timestamps) override;
 
  private:
   FRIEND_TEST_ALL_PREFIXES(ChromeExpectCTReporterTest, FeatureDisabled);