Commit ab5827e5 authored by Lucas Furukawa Gadani's avatar Lucas Furukawa Gadani Committed by Commit Bot

Add test that CSP frame-ancestors violations are reported.

Bug: 759184
Change-Id: I72c874798047f89c08271ba471d67baf04f2a920
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825899
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Reviewed-by: default avatarMike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700288}
parent 823f3f04
<!DOCTYPE html>
<html>
<head>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<title>Blocked frames are reported correctly</title>
</head>
<body>
<iframe src="support/content-security-policy.sub.html?policy=report-uri%20../../support/report.py%3Fop=put%26reportID={{$id:uuid()}}%3B%20frame-ancestors%20'none'"></iframe>
<script async defer src="../support/checkReport.sub.js?reportField=violated-directive&reportValue=frame-ancestors%20'none'&reportID={{$id}}"></script>
</body>
</html>
<!DOCTYPE html>
<html>
<body>
<p>This is an IFrame sending a Content Security Policy header containing "{{GET[policy]}}".</p>
</body>
</html>
This is a testharness.js-based test.
FAIL Violation report status OK. assert_equals: No such report. expected "" but got "false"
Harness: the test ran to completion.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment