github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 16:40:08 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #11824] Temporary workaround for Ollama Turbo new Bearer 🤔 ? #33606

New Issue
Closed
opened 2026-04-22 16:28:02 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-22 16:28:02 -05:00
Owner
Copy Link

Originally created by @LivioGama on GitHub (Aug 9, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11824

What is the issue?

I understood that it's the maintainers responsibility to implement the new field/headers token, and I agree.
But do you think it would be a lot of effort to (maybe temporarily) accept the bearer sent from the client this way? (GET query parameter)

Image

On ollama.com backend it would simply mean that after parsing the header, if it is empty, we try to get it as a url query parameters as a last resort

Originally created by @LivioGama on GitHub (Aug 9, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11824 ### What is the issue? I understood that it's the maintainers responsibility to implement the new field/headers token, and I agree. But do you think it would be a lot of effort to (maybe temporarily) accept the bearer sent from the client this way? (GET query parameter) <img width="1281" height="1030" alt="Image" src="https://github.com/user-attachments/assets/b92e7722-d4be-428a-9037-74ec8ede1c42" /> On `ollama.com` backend it would simply mean that after parsing the header, if it is empty, we try to get it as a url query parameters as a last resort
GiteaMirror added the cloudfeature request labels 2026-04-22 16:28:02 -05:00
GiteaMirror commented 2026-04-22 16:28:06 -05:00
Author
Owner
Copy Link

@ghmer commented on GitHub (Aug 9, 2025):

Not a great idea, imho - This token will most likely end up in at least one log file, rendering it effectively compromised.

<!-- gh-comment-id:3172068330 --> @ghmer commented on GitHub (Aug 9, 2025): Not a great idea, imho - This token will most likely end up in _at least_ one log file, rendering it effectively compromised.
GiteaMirror commented 2026-04-22 16:28:07 -05:00
Author
Owner
Copy Link

@attogram commented on GitHub (Aug 10, 2025):

Not for Ollama to do, but should be a request to jetbrains to support api bearer keys in their ai assist setup

<!-- gh-comment-id:3172256517 --> @attogram commented on GitHub (Aug 10, 2025): Not for Ollama to do, but should be a request to jetbrains to support api bearer keys in their ai assist setup
GiteaMirror commented 2026-04-22 16:28:07 -05:00
Author
Owner
Copy Link

@LivioGama commented on GitHub (Aug 13, 2025):

You are right @ghmer good catch.
@attogram done https://youtrack.jetbrains.com/issue/JBAI-16209/Support-Ollama-Turbo

<!-- gh-comment-id:3185691703 --> @LivioGama commented on GitHub (Aug 13, 2025): You are right @ghmer good catch. @attogram done https://youtrack.jetbrains.com/issue/JBAI-16209/Support-Ollama-Turbo
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label cloud feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#33606
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?