Update CSP policy #9836
Merged
Update CSP policy #9836
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PopDaph
approved these changes
Jan 8, 2025
|
Tested on front-edge moving forward with this |
|
Was not able to enforce a default-src without issue. Hopefully it will be enough for the scan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
For https://github.com/dust-tt/tasks/issues/1894
Stricten our CSP policy. Tesed in dev.
Viz is OK with this cc @fontanierh & @flvndvd
This is not absolutely great as we will have errors as we add new style or script integrations.
The script-src setting is supposed to be nextJS friendly and was tested locally
Will deploy to front-edge and test there before merging
Risk
High but easy to revert
Deploy Plan
front-edgeand testfront