feat: enforce strict CSP with per-request nonces#111
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Enforcing Content-Security-Policy on every HTML page: per-request nonce with strict-dynamic (official App Router pattern), built by the vitest-covered src/lib/csp.ts, wired in src/middleware.ts (nonce forwarded via request headers so Next stamps its inline scripts). Matcher widened to cover /login; authorized callback allows exactly /login and /login/ subpaths. API routes stay excluded (self-guarded via apiAuth). style-src keeps unsafe-inline (Tailwind/chart libs), documented trade-off. Verified: nonce rotates per request, auth redirects intact, zero console violations across the app including PDF export. Closes the strict CSP production-readiness item.