fix: HOTFIX openai provider empty Bearer when no apiKey configured #7803
+1
−1
Conversation
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
Should fix issue continuedev#7047 This enables using OpenAI-compatible APIs using other authentication methods than Bearer. I'm personally using basic auth with vLLM by configuring 'Authorization: Basic ...' in config.yaml which is thwarted by the openai provider adding an empty "Authorization: Bearer" even when no `apiKey is configured` which interferes with my custom Authorization header.
dosubot
bot
added
the
size:XS
|
All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
4 tasks
RomneyDa
changed the title
Patrick-Erichsen
approved these changes
Sep 17, 2025
Collaborator
Patrick-Erichsen
left a comment
Patrick-Erichsen
left a comment
There was a problem hiding this comment.
Thanks for the fix here!
Contributor
|
🎉 This PR is included in version 1.15.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Contributor
|
🎉 This PR is included in version 1.17.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Description
Should fix issue #7047
TL;DR: In openai provider, do not include an empty
Authorization: Bearerheader ifapiKeyhas not been configured.This enables using OpenAI-compatible APIs using other authentication methods than Bearer. I'm personally using basic auth with vLLM by configuring
Authorization: Basic ...in config.yaml which is thwarted by the openai provider adding an emptyAuthorization: Bearereven when noapiKeyis configured which interferes with my custom Authorization header.AI Code Review
@continue-general-reviewor@continue-detailed-reviewChecklist
Screen recording or screenshot
This is what HTTP headers used to look like for me before this fix:
Tests
None
Summary by cubic
Stop sending an empty Authorization: Bearer header in the OpenAI provider when no apiKey is configured. This lets OpenAI-compatible endpoints use other auth methods (e.g., Basic auth) without their custom Authorization header being overwritten.