Remove non-lowercase headers in Rails default configuration (fixes #541)#551
Merged
rei-moo merged 1 commit intogithub:feature-7.2from Dec 15, 2025
Merged
Conversation
…thub#541) While this gem now uses lowercase headers, the Rails default configuration still defines non-lowercase headers. As a result, our Railtie will not remove those conflicting headers. This change ensures that we're accounting for both lowercase and non-lowercase default headers in Rails.
Author
|
Any chance we can get a maintainer to review this? |
Contributor
|
Hey @obrie thanks for the contribution! Sorry for the delay. This is on our radar and we will be taking a look shortly. 😄 |
rei-moo
approved these changes
Dec 15, 2025
Contributor
rei-moo
left a comment
rei-moo
left a comment
There was a problem hiding this comment.
Looks good, thank you! 🎉
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.
This implements the solution proposed in #541
The full details of the issue can are described in that ticket. To summarize:
While secure_headers now uses lowercase headers (as required by Rack 3+), the Rails default configuration still defines non-lowercase headers. As a result, our Railtie will not remove those conflicting headers.
This change ensures that we're accounting for both lowercase and non-lowercase default headers in Rails (for current Rails defaults and future defaults).
All PRs:
Adding a new header
Generally, adding a new header is always OK.
Adding a new CSP directive