Implement ContentSecurityPolicy on the browser-side.

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

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "core/frame/csp/CSPSource.h"
 
 #include "core/frame/UseCounter.h"
 #include "core/frame/csp/ContentSecurityPolicy.h"
 #include "platform/weborigin/KURL.h"
 #include "platform/weborigin/KnownPorts.h"
@@ skipping 187 matching lines @@
     for (const auto& sourceA : listA) {
       if ((foundMatch = sourceA->subsumes(sourceB)))
         break;
     }
     if (!foundMatch)
       return false;
   }
   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);
 }
 
 }  // namespace blink