fix(security): add missing HTTP security headers (#2013)#2014
Merged
dipexplorer merged 1 commit intoJun 17, 2026
Merged
Conversation
github-actions
Bot
added
gssoc:approved
dipexplorer
added
level:critical
github-project-automation
Bot
moved this from 📥 Backlog
to 🎉 Merged
in SahiDawa Workflow
Contributor
|
🎉 Congratulations @PremSahith! Your Pull Request "fix(security): add missing HTTP security headers (#2013)" has been successfully merged by @dipexplorer. Thank you for your valuable contribution to SahiDawa! 🇮🇳 Follow us on LinkedIn: https://www.linkedin.com/company/ratloopz/ to get shoutout |
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
2 participants
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.
🛑 STOP: Assignment & File Scope Check
Warning
PRs with unrelated files will not be reviewed and may be closed.
📋 PR Summary & Link
next.config.mjsto protect the application against XSS, clickjacking, and other common vulnerabilities. The previous configuration only included aVary: Accept-Encodingheader for API routes, which has been successfully preserved.📸 Proof of Work (Screenshots / Logs)
Important
No Pull Request will be merged without proof of testing!
Please drag & drop your screenshots/GIFs here:
(Since this is a configuration change without visible UI updates, I recommend running the app locally, opening the browser's Network tab, and taking a screenshot of the response headers for the document request to show that the new security headers are present. You can drag and drop that screenshot here.)
🏷️ PR Type
type: bugtype: featuretype: docstype: testingtype: securitytype: performancetype: designtype: refactortype: devopstype: accessibility✅ Checklist
Closes #2013)mainand resolved any conflicts