Implement ContentSecurityPolicy on the browser-side.

third_party/WebKit/Source/core/frame/csp/CSPSource.cpp

Index: third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
diff --git a/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp b/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
index 3b5ed5cce1c5cc84c004ccdbf3283fdcdd77ed51..43c5c0816acf0e377075553a03985c4512e382f9 100644
--- a/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
+++ b/third_party/WebKit/Source/core/frame/csp/CSPSource.cpp
@@ -205,6 +205,17 @@ bool CSPSource::firstSubsumesSecond(
   return true;
 }
 
+WebContentSecurityPolicySourceExpression CSPSource::expose() const {
+  WebContentSecurityPolicySourceExpression sourceExpression;
+  sourceExpression.scheme = m_scheme;
+  sourceExpression.host = m_host;
+  sourceExpression.isHostWildcard = (m_hostWildcard == HasWildcard);

[Mike West, 2017/02/13 14:10:51]

Nit: It seems like we should either use booleans on both sides of the platform
divide, or enums on both sides. Is there a good reason to change this to enums?
Blink usually prefers more descriptive names...

[arthursonzogni, 2017/02/14 17:07:03]

Okay, let's use an enum in blink.

+  sourceExpression.port = m_port;
+  sourceExpression.isPortWildcard = (m_portWildcard == HasWildcard);
+  sourceExpression.path = m_path;
+  return sourceExpression;
+}
+
 DEFINE_TRACE(CSPSource) {
   visitor->trace(m_policy);
 }