Content - 9a264f2a240bfb89b29aeee7ec39fb1e035b0f52 - 0d65929/content-security-policy/script-src/worker-eval-blocked.sub.html

visit type:

Tip revision: 34bd5b1a3394e0ffcae29aae509057bfd1fa3935 authored by Yutaka Hirano on 03 April 2018, 03:15:14 UTC
fix

Tip revision: 34bd5b1

worker-eval-blocked.sub.html

<!DOCTYPE html>
<html>

<head>
    <!-- Programmatically converted from a WebKit Reftest, please forgive resulting idiosyncracies.-->
    <meta http-equiv="Content-Security-Policy" content="script-src 'self' 'unsafe-inline'; connect-src 'self';">
    <title>worker-eval-blocked</title>
    <script src="/resources/testharness.js"></script>
    <script src="/resources/testharnessreport.js"></script>
    <script src='../support/logTest.sub.js?logs=["eval blocked"]'></script>
    <script src='../support/alertAssert.sub.js?alerts=[]'></script>
</head>

<body>
    <p>This test loads a worker, delivered with its own policy.
    The eval() call in the worker should be forbidden by that
    policy.  No report should be generated because the worker
    policy does not set a report-uri (although this parent
    resource does).</p>
    <script>
        window.addEventListener('securitypolicyviolation', function(e) {
            log('Fail');
        });
    
        try {
            var worker = new Worker('/content-security-policy/script-src/support/worker-eval.js');
            worker.onmessage = function(event) {
                log(event.data);
            };
        } catch (e) {
            log(e);
        }

    </script>
    <div id="log"></div>
</body>

</html>

Browse the archive

https://github.com/web-platform-tests/wpt