Remove X-Powered-By header #1111
Merged
Conversation
This file contains 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
alxndrsn
reviewed
Mar 23, 2024
| const { headers } = await service.get('/v1/users/current'); | ||
| should(headers['x-powered-by']).be.undefined(); | ||
| })); | ||
| }); |
There was a problem hiding this comment.
Haha, yeah, I cherry picked. The commit says it's authored by you so not sure why it's showing my face!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follows the OWASP recommendation: https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html#x-powered-by
This is not super important because there are many other ways to learn about the stack but it does get flagged by some security scanners.
What has been done to verify that this works as intended?
Ran it, looked at headers in console
Why is this the best possible solution? Were any other approaches considered?
I think this is the only approach!
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Should have no risk of negative effect.
Does this change require updates to the API documentation? If so, please update docs/api.md as part of this PR.
No.
Before submitting this PR, please make sure you have:
make testand confirmed all checks still pass OR confirm CircleCI build passes