Repository navigation
[Fix] API-key integrations lose schemes when Authorization uses mixed case - #3487
Closed
roomote-roomote[bot] wants to merge 1 commit into
Closed
roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
October 15, 2026 06:20
This was referenced Oct 15, 2026
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
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.
Related issue
Internal maintainer-requested correctness work; no issue opened.
Why this PR exists
Entering
Authorizationor padded uppercaseAUTHORIZATIONshows a Scheme selector, but saving drops the selected Bearer/Token prefix. The header name is normalized while the prefix condition checks the raw casing.What changed
Normalize the submitted header name once and use it for both the header and scheme condition. Standard lowercase Authorization and custom-header behavior stay unchanged. No new state, controls, dependencies, API or schema changes.
How it was tested
authorizationwith an empty prefix despite the visible Bearer choice. Case/whitespace payload regressions fail on that baseline.32f9903dea9ee7acd11dd4e873535b8bcc83611b: real shared desktop mixed-case Bearer save, personal mobile padded-uppercase Token save, and customX-API-Keyempty-prefix control all persist the selected metadata through the local API/PostgreSQL. Each fixture was removed through the normal confirmation flow, then physically cleaned up; zero fixture rows remain.Checklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locallypnpm changesetRelated PRs