Repository navigation
fix(ide-client): normalize Authorization header to avoid invalid Bearer prefix - #2
Merged
Merged
Conversation
…ing Bearer prefix do not produce an invalid header
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.
Summary
Hardens
SpockifyHttpClientso an API key that already contains aBearerprefix (from keyring storage, settings UI, or copy-paste) does not produce a malformedAuthorizationheader such asBearer Bearer sk-….This was observed on Linux (Fedora + COSMIC) where the OS keyring path could surface the key differently than on Windows, leading to
headers.seterrors or rejected requests.Changes
normalizeApiKey()that strips a leadingBearer(case-insensitive) and trims whitespace.Authorization: Bearer <token>header.Test plan
sk-…key and confirm chat / model list works.Bearer sk-…and confirm the same (no double prefix).