Closed
Bug 1695498
Opened 5 years ago
Closed 5 years ago
[wpt-sync] Sync PR 27816 - Test CSP hash-algorithm case-insensitive matching
Categories
(Core :: DOM: Security, task, P4)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
88 Branch
| Tracking | Status | |
|---|---|---|
| firefox88 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream][domsecurity-backlog])
Sync web-platform-tests PR 27816 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/27816
Details from upstream follow.
b'Michael[tm] Smith <mike@w3.org>' wrote:
Test CSP hash-algorithm case-insensitive matching
This tests that the hash-algorithm parts of CSP hash sources are matched case-insensitively. See https://github.com/w3c/webappsec-csp/pull/464
| Assignee | ||
Updated•5 years ago
|
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
| Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream][domsecurity-backlog] → [wptsync downstream]
| Assignee | ||
Comment 1•5 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=912e93283ef854a141e83ba1caf8399d8806e2bd
| Assignee | ||
Comment 2•5 years ago
|
||
CI Results
Ran 15 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 2 tests and 1 subtests
Status Summary
Firefox
OK : 2
PASS: 2
Chrome
OK : 2
PASS: 2
Safari
OK : 2
PASS: 2
Links
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2e6af565cc2a
[wpt PR 27816] - Test CSP hash-algorithm case-insensitive matching, a=testonly
Comment 4•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox88:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•