Closed
Bug 1735476
Opened 3 years ago
Closed 3 years ago
ensure that logging for content security checks (CSMLog) is fully conformant YAML
Categories
(Core :: DOM: Security, task, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
95 Branch
Tracking | Status | |
---|---|---|
firefox95 | --- | fixed |
People
(Reporter: freddy, Assigned: freddy)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
Turns out (d'oh), that this is great yaml to list an object:
key: value
key2: value
and this is creating a list single (key, value) objects
- key: value
- key2: value
We want the former.
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [domsecurity-active]
Assignee | ||
Comment 1•3 years ago
|
||
This commit changes the MOZ_LOG to make the yaml easier to parse,
addressing various shortcomings:
- Firstly, the yaml "document" for a check was an array of dictionaries
that each contained a single key/value pair. It's now a big dictionary
containing lots of key/value pairs instead. - Indentation was wrong for some of the attributes of the content
security check - The name key-name for https-only flags was oddly cased
This changeset resolves all of these shortcomings.
Pushed by fbraun@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e38012c0a4ea MOZ_LOG=CSMLog emits contentsecuritycheck as valid yaml r=ckerschb
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox95:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•