Skip to content

fix(security): correct clickjacking headers for web routes - #315

Open
jdotc1 wants to merge 1 commit into
TripSit:uatfrom
jdotc1:fix/298-clickjacking-headers
Open

jdotc1 wants to merge 1 commit into
TripSit:uatfrom
jdotc1:fix/298-clickjacking-headers

Conversation

@jdotc1

@jdotc1 jdotc1 commented Nov 13, 2026

Copy link
Copy Markdown

Closes #298.

Apply X-Frame-Options: SAMEORIGIN (rather than an invalid value) alongside CSP frame-ancestors 'self' on every Next.js page/route, and disable the framework signature header. Includes a Jest regression test for both policies.

Verification: node --check next.config.js, direct header-policy Node smoke check, and git diff --check passed. Full Jest/Next test suite not run: npm ci was blocked by the environment refusing the repository's Git-hosted tripsit_drug_db dependency (EALLOWGIT), unrelated to the patch. Production Traefik middleware may also set/override response headers; the deployed response should be checked after merge.

Targeting uat per CONTRIBUTING.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

X-Frame-Options has an invalid value, so the site can be framed

1 participant