Adding Embedding-CSP HTTP header

third_party/WebKit/Source/core/html/HTMLIFrameElement.cpp

Index: third_party/WebKit/Source/core/html/HTMLIFrameElement.cpp
diff --git a/third_party/WebKit/Source/core/html/HTMLIFrameElement.cpp b/third_party/WebKit/Source/core/html/HTMLIFrameElement.cpp
index 9e956903a26e651ea66d4c1b3b3acaba6a5a5507..624356c00d5b03028472c1ea5f9748af182d25be 100644
--- a/third_party/WebKit/Source/core/html/HTMLIFrameElement.cpp
+++ b/third_party/WebKit/Source/core/html/HTMLIFrameElement.cpp
@@ -121,6 +121,10 @@ void HTMLIFrameElement::parseAttribute(const QualifiedName& name, const AtomicSt
         if (initializePermissionsAttribute())
             m_permissions->setValue(value);
     } else if (RuntimeEnabledFeatures::embedderCSPEnforcementEnabled() && name == cspAttr) {
+        if (!value.getString().containsOnlyASCII()) {
+            document().addConsoleMessage(ConsoleMessage::create(OtherMessageSource, ErrorMessageLevel, "'csp' attribute contains non-ASCII characters: " + value));

[Mike West, 2016/09/30 13:11:49]

This has the side-effect of putting `m_csp` and the attribute's value out of
sync. I'd suggest we clear out `m_csp` if the content attribute is invalid (and
update the spec accordingly).

+            return;
+        }
         AtomicString oldCSP = m_csp;
         m_csp = value;
         if (m_csp != oldCSP)