Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow additive csp configuration #102059
Allow additive csp configuration #102059
Changes from 9 commits
80ecded
73890df
303d60a
b3d60b2
ee9f805
c8eccd5
d531ac0
dca375f
4b45111
ca5616d
2188b0e
0d3bd2c
400b2d1
e1eb1b5
42c81ec
227c5b7
592a119
383aa95
ec383c3
8a28a62
c74ada5
59303f4
3d7947c
3609981
966fc55
04a4f59
e9590d4
fff64d8
46681a3
596db0d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forbidding both usages simultaneously was what we talked about. Technically we could allow it, as the new
CspDirectives
system could merge both sources though, but it's probably better to just not mix thingsThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure it's the best wording, suggestions welcome
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These tests are effectively mostly testing the
CspDirectives
class, but I thought it made sense to still test the config configuration / behavior without mocking the underlying implementation (to preserve the implementation during test isolation)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The partial constructor thingy was just a workaround to instantiate the
default
config. Adapted for better consistency with our other config classes (and also because it didn't make a lot of sense imho)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that we're supporting additive config, I'm not sure the
rawCspConfig.rules?.length
part of the if condition makes sense, as we're now capable of adding additional rules even ifframe-ancestors
is already specified. WDYT?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self: we can probably remove this warning feature now that we no longer support IE11