Parameterize and Update CORS and CSP #244
Merged
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
Update CORS and CSP
Convert CORS and CSP settings to environment variables.
Add variables to dev.env.example for local testing
Delete constants.js file
💭 Motivation and context
Updated CORS and CSP improve site security limiting which websites can request resources from our API. This reduces the risk of cross-site request forgery (CSRF) and data leakage, as only listed origins are allowed to interact with our server.
Parameterizing these settings allows us to change them using the AWS console without initiating a new deployment.
closes issue #241
🧪 Testing
All tests pass and site functions as expected. Full testing requires deployment to DMZ staging.
You must add the following new environment variables from dev.env.example to your .env file for your local environment to work.
✅ Pre-approval checklist
in code comments.
✅ Pre-merge checklist
✅ Post-merge checklist