Include unverified server-sent cert chain in reports

chrome/browser/ssl/cert_logger.proto

Index: chrome/browser/ssl/cert_logger.proto
diff --git a/chrome/browser/ssl/cert_logger.proto b/chrome/browser/ssl/cert_logger.proto
index d53b8480a011d4d056fed5ac75993491a3b9c7b3..bb11bf29266527e772547a1d1edcffa5e9cda083 100644
--- a/chrome/browser/ssl/cert_logger.proto
+++ b/chrome/browser/ssl/cert_logger.proto
@@ -83,4 +83,10 @@ message CertLoggerRequest {
   // Information about the interstitial that was shown to the user for
   // this certificate error.
   optional CertLoggerInterstitialInfo interstitial_info = 7;
+
+  // The unverified certificate chain as received by the client, as a
+  // series of PEM-encoded certificates. Can be different than
+  // |cert_chain|, which is the chain the client built during
+  // verification.
+  optional string unverified_cert_chain = 8;

[meacer, 2015/06/15 19:57:20]

Just to clarify: Should we always expect this not to be empty? Does caching etc.
change whether |unverified_cert_chain| will be empty?

[estark, 2015/06/15 20:47:36]

I believe we should always expect it to be non-empty. SSLInfo::unverified_cert
will be empty for resources that were loaded from cache, but since we are
sending reports for pages that have certificate errors and we don't cache
resources with certificate errors, this should always be filled. (That is, if we
are showing an interstitial page, I don't think the page could have been loaded
from cache.) Should I add a comment explaining that, or is too much detail?

 };