Addition of Certificate Transparency details to Security panel of DevTools

third_party/WebKit/Source/platform/exported/WebURLResponse.cpp

Index: third_party/WebKit/Source/platform/exported/WebURLResponse.cpp
diff --git a/third_party/WebKit/Source/platform/exported/WebURLResponse.cpp b/third_party/WebKit/Source/platform/exported/WebURLResponse.cpp
index 1766df4cfbb2ab2ed61983fab6b127f41abec122..05be131a4970e092ab3e29e0d66c9e6b6e2c2735 100644
--- a/third_party/WebKit/Source/platform/exported/WebURLResponse.cpp
+++ b/third_party/WebKit/Source/platform/exported/WebURLResponse.cpp
@@ -323,6 +323,9 @@ void WebURLResponse::setSecurityStyle(SecurityStyle securityStyle)
 
 void WebURLResponse::setSecurityDetails(const WebSecurityDetails& webSecurityDetails)
 {
+    blink::ResourceResponse::SignedCertificateTimestampList sctList;
+    for (const auto& iter : webSecurityDetails.sctList)
+        sctList.append(static_cast<blink::ResourceResponse::SignedCertificateTimestamp>(iter));

[Mike West, 2016/06/23 16:32:30]

It surprises me a little bit that this works. You're static_casting a
`blink::WebURLRequest::SignedCertificateTimestamp` to
`blink::ResourceResponse::SignedCertificateTimestamp` whose attributes have
different types. Why doesn't that explode?

     m_private->m_resourceResponse->setSecurityDetails(
         webSecurityDetails.protocol,
         webSecurityDetails.keyExchange,
@@ -331,7 +334,8 @@ void WebURLResponse::setSecurityDetails(const WebSecurityDetails& webSecurityDet
         webSecurityDetails.certId,
         webSecurityDetails.numUnknownScts,
         webSecurityDetails.numInvalidScts,
-        webSecurityDetails.numValidScts);
+        webSecurityDetails.numValidScts,
+        sctList);
 }
 
 ResourceResponse& WebURLResponse::toMutableResourceResponse()