Add standard security headers (HSTS, CSP, etc.) #42
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.
Implemented standard security headers in the HTTP transport layer to improve the application's security posture.
Security Enhancements:
default-src 'none', strictly blocking all external resources and inline scripts. This is appropriate for an API-only service and significantly reduces XSS risks.max-age=31536000), including subdomains. This is applied conditionally: only when the request is secure (HTTPS) or the environment isproduction, preventing issues during local development.Verification:
src/security-headers.test.tswhich verified the presence and correctness of all headers.npm test).PR created automatically by Jules for task 3274137449072602053 started by @davidruzicka