-
Notifications
You must be signed in to change notification settings - Fork 7
add default enforced Content Security Policy #135
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
Merged
Merged
Conversation
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
Contributor
labkey-stuartm
left a comment
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.
There is a typo in the ReadMe changes
"In can, however,"
This should be:
It can, however,
labkey-jony
approved these changes
Feb 14, 2025
Co-authored-by: labkey-stuartm <32204841+labkey-stuartm@users.noreply.github.com>
labkey-stuartm
approved these changes
Feb 14, 2025
labkey-willm
added a commit
that referenced
this pull request
Feb 14, 2025
* add default csp.enforce block and ability to load an optional.application.properties * remove CSP_REPORT and CSP_ENFORCE; update README * add wiring for optional app properties file from s3 * update to match what's currently deployed * Update README.md Co-authored-by: labkey-stuartm <32204841+labkey-stuartm@users.noreply.github.com> --------- Co-authored-by: labkey-stuartm <32204841+labkey-stuartm@users.noreply.github.com>
labkey-willm
added a commit
that referenced
this pull request
Feb 15, 2025
* add default csp.enforce block and ability to load an optional.application.properties * remove CSP_REPORT and CSP_ENFORCE; update README * add wiring for optional app properties file from s3 * update to match what's currently deployed * Update README.md --------- Co-authored-by: labkey-stuartm <32204841+labkey-stuartm@users.noreply.github.com>
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.
Rationale
https://github.com/LabKey/kanban/issues/362
We are consolidating where we are defining our default Content Security Policy, and making 'enforce' the default for most, if not all, deployments.
Related Pull Requests
Changes