Quality: Add security headers and CSP to block malicious domains#353
Open
andoan16 wants to merge 1 commit into
Open
Conversation
Create Next.js configuration file with security headers including Content Security Policy (CSP) to prevent the browser from loading resources from the suspicious domains mentioned in the issue (infoworldbriefs.com, changelesschoir.com, signedquick.com) and to mitigate the impact of any potential injection vulnerabilities. Affected files: next.config.ts Signed-off-by: andoan16 <33853760+andoan16@users.noreply.github.com>
|
HSTS should not be set here. |
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
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.
Problem
Create Next.js configuration file with security headers including Content Security Policy (CSP) to prevent the browser from loading resources from the suspicious domains mentioned in the issue (infoworldbriefs.com, changelesschoir.com, signedquick.com) and to mitigate the impact of any potential injection vulnerabilities.
Severity:
criticalFile:
next.config.tsSolution
Create next.config.ts with the following content:
Changes
next.config.ts(new)Testing
Closes #339