aboutsummaryrefslogtreecommitdiffstats
path: root/tests/wpt/meta/encoding/textdecoder-byte-order-marks.any.js.ini
diff options
context:
space:
mode:
authorTim van der Lippe <TimvdLippe@users.noreply.github.com>2025-04-25 21:59:44 +0200
committerGitHub <noreply@github.com>2025-04-25 19:59:44 +0000
commitbaa18e18afa20f3b38c17c830feb76b05f7e64fb (patch)
treed73a1bf7432f1226b427ef2ea2c9ff1f3acc0420 /tests/wpt/meta/encoding/textdecoder-byte-order-marks.any.js.ini
parent4ff45f86b9af63edafd98685f9d73e8a250ff9aa (diff)
downloadservo-main.tar.gz
servo-main.zip
Support CSP report-only header (#36623)HEADmain
This turned out to be a full rabbit hole. The new header is parsed in the new `parse_csp_list_from_metadata` which sets `disposition` to `report. I was testing this with `script-src-report-only-policy-works-with-external-hash-policy.html` which was blocking the script incorrectly. Turns out that there were multiple bugs in the CSP library, as well as a missing check in `fetch` to report violations. Additionally, in several locations we were manually reporting csp violations, instead of the new `global.report_csp_violations`. As a result of that, they would double report, since the report-only header would be appended as a policy and now would report twice. Now, all callsides use `global.report_csp_violations`. As a nice side-effect, I added the code to set source file information, since that was already present for the `eval` check, but nowhere else. Part of #36437 Requires servo/rust-content-security-policy#5 --------- Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com> Signed-off-by: Tim van der Lippe <TimvdLippe@users.noreply.github.com>
Diffstat (limited to 'tests/wpt/meta/encoding/textdecoder-byte-order-marks.any.js.ini')
0 files changed, 0 insertions, 0 deletions