fix: add CSP and security headers for frontend deployment#189
Merged
Conversation
Configure Netlify _headers with: - CSP restricting scripts to self, styles to self + unsafe-inline (required by Tailwind), connections to Stacks API and CoinGecko, images to self + data + https, and frame-ancestors to none - X-Frame-Options: DENY to prevent clickjacking - X-Content-Type-Options: nosniff to prevent MIME sniffing - Referrer-Policy: strict-origin-when-cross-origin - Permissions-Policy restricting camera, microphone, geolocation
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.
Closes #85
Changes
Add Netlify
_headersfile with comprehensive security headers:These headers protect the financial application from XSS, clickjacking, and data injection attacks.