third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-script-reportonly-blocked.php - Issue 2056183002: Implement the `require-sri-for` CSP directive

Unified Diff: third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-script-reportonly-blocked.php

Issue 2056183002: Implement the `require-sri-for` CSP directive (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Updated tests Created 4 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-script-reportonly-allowed.php ('k') | third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-serviceworker-blocked.php » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-script-reportonly-blocked.php

diff --git a/third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-script-reportonly-blocked.php b/third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-script-reportonly-blocked.php

new file mode 100644

index 0000000000000000000000000000000000000000..eec344bdd40d4efdb3dd454ecb8568be8dd1ab9d

--- /dev/null

+++ b/third_party/WebKit/LayoutTests/http/tests/security/contentSecurityPolicy/require-sri-for/require-sri-for-script-reportonly-blocked.php

@@ -0,0 +1,25 @@

+<!-- <?php

+ // TODO(mkwst) enable after windows hash differences are fixed

+ header("Content-Security-Policy-Report-Only: require-sri-for script; script-src 'self' 'unsafe-inline'");

+?> -->

Mike West 2016/07/14 05:25:07 I'd prefer for you to adjust the test to expect th

Sergey Shekyan 2016/07/14 06:52:39 I cannot figure out how to expect the failure with

+<!doctype html>

+<script src="/resources/testharness.js"></script>

+<script src="/resources/testharnessreport.js"></script>

+<script>

+ // TODO(mkwst) enable after windows hash differences are fixed

+ // async_test(t => {

+ // var watcher = new EventWatcher(t, document, ['securitypolicyviolation']);

+ // watcher

+ // .wait_for('securitypolicyviolation')

+ // .then(t.step_func_done(e => {

+ // assert_equals(e.blockedURI, "http://127.0.0.1:8000/security/contentSecurityPolicy/require-sri-for/ran.js");

+ // }));

+ // }, "Script without integrity generates reports.");

+ var executed_test = async_test("Script that requires integrity executes and generates a violation report.");

+</script>

+<script src="ran.js"></script>

+<script>

+ assert_equals(z, 13);

+ executed_test.done();

+</script>