Content - 229667e7d6643aa47f38a7139d5f5f98ba7e1fa0 - 08e1813/content-security-policy/blink-contrib/eval-blocked.sub.html

visit type:

Tip revision: 081d5deaff4a25ca5f8b6c0baa30e085de230c36 authored by Mike West on 13 September 2015, 08:25:34 UTC
CSP: Correct a cookie name.

Tip revision: 081d5de

eval-blocked.sub.html

<!DOCTYPE html>
<html>

<head>
    <!-- Programmatically converted from a WebKit Reftest, please forgive resulting idiosyncracies.-->
    <title>eval-blocked</title>
    <script src="/resources/testharness.js"></script>
    <script src="/resources/testharnessreport.js"></script>
    <script src='../support/logTest.sub.js?logs=["PASS EvalError","PASS EvalError"]'></script>
    <script src="../support/alertAssert.sub.js?alerts=[]"></script>
    <!-- enforcing policy:
script-src 'self' 'unsafe-inline' 'unsafe-inline'; connect-src 'self';
-->
</head>

<body>
    <script>
        try {
            eval("alert_assert('FAIL (1 of 2)')");
        } catch (e) {
            log("PASS EvalError");
        }

    </script>
    <script>
        try {
            window.eval("alert_assert('FAIL (1 of 2)')");
        } catch (e) {
            log("PASS EvalError");
        }

    </script>
    <div id="log"></div>
    <script async defer src="../support/checkReport.sub.js?reportExists=true&amp;reportField=violated-directive&amp;reportValue=script-src%20&apos;unsafe-inline&apos;"></script>
</body>

</html>

Browse the archive

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