ollama/ollama-python
1
0
Fork 0
mirror of https://github.com/ollama/ollama-python.git synced 2026-07-21 09:05:23 -04:00
Code Issues 101 Packages Projects Releases 10 Wiki Activity

Get custom headers in ChatResponse #188

New Issue
Open
opened 2026-02-15 16:28:34 -05:00 by yindo · 5 comments
yindo commented 2026-02-15 16:28:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @lasseedfast on GitHub (Dec 13, 2024).

Originally assigned to: @ParthSareen on GitHub.

I'm using an Nginx server to direct requests made with the Ollama Python library to different running Ollama servers. The Nginx server selects an Ollama server based on availability, among other factors, and sends that information in the X-Choosen-Server header. Using Python's requests library, I can receive this header in the response. However, when using Ollama, it seems like I can't.
Have I overlooked something, or would it be possible to implement custom headers in the ChatResponse?

Originally created by @lasseedfast on GitHub (Dec 13, 2024). Originally assigned to: @ParthSareen on GitHub. I'm using an Nginx server to direct requests made with the Ollama Python library to different running Ollama servers. The Nginx server selects an Ollama server based on availability, among other factors, and sends that information in the `X-Choosen-Server` header. Using Python's `requests` library, I can receive this header in the response. However, when using Ollama, it seems like I can't. Have I overlooked something, or would it be possible to implement custom headers in the `ChatResponse`?
yindo commented 2026-02-15 16:28:34 -05:00
Author
Owner
Copy Link
Copy Source

@ParthSareen commented on GitHub (Dec 18, 2024):

Hey! You should be able to pass in httpx client options directly into the Client instantiation as they are a pass through. Give that a shot and lmk if you run into issues :)

@ParthSareen commented on GitHub (Dec 18, 2024): Hey! You should be able to pass in httpx client options directly into the `Client` instantiation as they are a pass through. Give that a shot and lmk if you run into issues :)
yindo commented 2026-02-15 16:28:34 -05:00
Author
Owner
Copy Link
Copy Source

@lasseedfast commented on GitHub (Dec 18, 2024):

Thanks! Maybe I wasn't clear with the problem – I have tried to pass in options into to Client, but I don't understand how to receive other data than that included in the Ollama ChatRequest object, although the Nginx server in the middle are sending things like X-Headers along with the Ollama response.

@lasseedfast commented on GitHub (Dec 18, 2024): Thanks! Maybe I wasn't clear with the problem – I have tried to pass in options _into_ to `Client`, but I don't understand how to _receive_ other data than that included in the Ollama `ChatRequest` object, although the Nginx server in the middle are sending things like X-Headers along with the Ollama response.
yindo commented 2026-02-15 16:28:35 -05:00
Author
Owner
Copy Link
Copy Source

@ParthSareen commented on GitHub (Dec 18, 2024):

Ahhh I see what you mean - sorry about that. Let me dig into this a bit and see if there's a good pattern we can expose. We definitely do not support this now. For my knowledge - do you need to know the return of what nginx returns? Is this throwing an error or is it a "good to know/nice to have"

@ParthSareen commented on GitHub (Dec 18, 2024): Ahhh I see what you mean - sorry about that. Let me dig into this a bit and see if there's a good pattern we can expose. We definitely do not support this now. For my knowledge - do you need to know the return of what nginx returns? Is this throwing an error or is it a "good to know/nice to have"
yindo commented 2026-02-15 16:28:35 -05:00
Author
Owner
Copy Link
Copy Source

@lasseedfast commented on GitHub (Dec 19, 2024):

I would love to know the return! In this case it's a string, more precise an internal IP and port number (one of the running Ollama servers) but I imagine there are other use cases as well. And it's not throwing an error, as I understand the CharRequest.model_dump method it checks the response from the server – normally an Ollama instance but this time the Nginx proxy – and includes all values that are specified but I'm not very familiar with the typing library and this is also why I don't try to solve this myself...

@lasseedfast commented on GitHub (Dec 19, 2024): I would love to know the return! In this case it's a string, more precise an internal IP and port number (one of the running Ollama servers) but I imagine there are other use cases as well. And it's not throwing an error, as I understand the `CharRequest.model_dump` method it checks the response from the server – normally an Ollama instance but this time the Nginx proxy – and includes all values that are specified but I'm not very familiar with the `typing` library and this is also why I don't try to solve this myself...
yindo commented 2026-02-15 16:28:35 -05:00
Author
Owner
Copy Link
Copy Source

@ParthSareen commented on GitHub (Dec 19, 2024):

Okay! Appreciate the explanation. Will leave this issue open for now and think about how we can possibly do this. Thank you!

@ParthSareen commented on GitHub (Dec 19, 2024): Okay! Appreciate the explanation. Will leave this issue open for now and think about how we can possibly do this. Thank you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
 thinking
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ollama/ollama-python#188
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?