fix: hide X-Powered-By header via Firebase hosting config#398
Merged
Aditya948351 merged 1 commit intoMay 31, 2026
Merged
Conversation
Aditya948351
approved these changes
May 31, 2026
Collaborator
Aditya948351
left a comment
Aditya948351
left a comment
There was a problem hiding this comment.
Excellent security hygiene hiding the X-Powered-By header via firebase.json. Approved!
Collaborator
|
Do star the repo! Successfully merging this and loved the changes you did. |
Aditya948351
added
gssoc26
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.
Fix #361
What does this PR do?
Hides the X-Powered-By header to prevent leaking technology
stack details to potential attackers.
Changes Made
firebase.jsonto removethe X-Powered-By header from all responses
Research
This project uses Next.js with
output: 'export'deployedon Firebase Hosting (static). Since there is no Express
backend, middleware-based solutions won't work here.
Configuring headers directly in
firebase.jsonis thecorrect approach for this setup.
Why?
Exposing the X-Powered-By header reveals the technology stack
to attackers, making it easier to target known vulnerabilities.