Remove unsafe-inline from CSP and fix syntax errors #2536
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
Removes
'unsafe-inline'from thestyle-srcContent Security Policy directive in the Caddy configuration, eliminating an XSS attack vector. Also corrects invalid double semicolons in the CSP syntax.Fixes #(issue number for unsafe-inline CSP security risk)
Changes:
'unsafe-inline'fromstyle-srcdirective infrontend/Caddyfiledefault-srcandscript-srcdirectives to single semicolonsThe application uses only external stylesheets (Vite-bundled CSS, Bootstrap, Google Fonts, FontAwesome). No inline styles exist in source or build output.
Type of change
How Has This Been Tested?
Verified existing unit tests pass and frontend builds successfully.
Checklist
Further comments
CSP
'unsafe-inline'allows arbitrary inline styles, which can be injected by attackers. Modern frontend tooling (Vite, React) compiles all styles to external CSS files, making this directive unnecessary and a security liability.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.