feat(CSP): add 'trusted-types' CSP directive support #58
Conversation
add possibility to specify 'trusted-types' and 'require-trusted-types-for' CSP directives re juunas11#57
| public CspRequireSriBuilder RequireSri { get; } = new CspRequireSriBuilder(); | ||
|
|
||
| /// <summary> | ||
| /// Setups up rules for controlling when to restrict the creation of Trusted Types policies |
There was a problem hiding this comment.
Typo: "Setups up" -> "Sets up". I do notice this typo is in existing code as well :\
It could be good to link to the MDN documentation here.
| return this; | ||
| } | ||
|
|
||
| public CspTrustedTypesBuilder RequireTrustedTypesForScript() |
There was a problem hiding this comment.
I think this function needs a comment explaining what effect it has.
| /// Allow CSS from the given | ||
| /// <paramref name="policyName"/>. | ||
| /// </summary> | ||
| /// <param name="policyName">A valid policy name consists only of alphanumeric characters, or one of "-#=_/@.%". </param> |
There was a problem hiding this comment.
If there is a valid set of characters, should we validate it?
|
|
||
| /// <summary> | ||
| /// Instructs user agents to control the data passed to DOM XSS sink functions, like Element.innerHTML setter. | ||
| /// Those functions only accept non-spoofable, typed values created by Trusted Type policies, and reject strings. |
There was a problem hiding this comment.
This comment could use an MDN link as well.
|
|
||
|
|
||
| [Fact] | ||
| public void RequireTrustedTypes_ReturnsCorrectHeader() |
There was a problem hiding this comment.
A couple more unit tests would be nice. At least one with a specific policy name and one that sets up the require-trusted-types-for directive.
|
Any chance of reviving this? |
3 participants
add possibility to specify 'trusted-types' and 'require-trusted-types-for' CSP directives
re #57