Enable "enforce" CSP for dev deployments#956
Merged
labkey-tchad merged 2 commits intodevelopfrom Dec 20, 2024
Merged
Conversation
labkey-adam
approved these changes
Dec 19, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Rationale
Now that we've deployed "enforce" CSP to production servers, we should have developers run with it locally. Not enabling it by default on TeamCity because tests reliably check for CSP errors where developers might not.
The
useLocalBuildparameter is a good proxy for non-TeamCity dev deployments.Related Pull Requests
Changes
application.properties