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

[PR #10813] api: improve HTTP client security configuration #13373

New Issue
Open
opened 2026-04-13 00:25:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 00:25:17 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/ollama/ollama/pull/10813

State: open
Merged: No

This changes Ollama to use more secure and robust HTTP client configurations in the API package. The changes include:

  • Improved timeout configurations for better reliability
  • Enhanced transport security settings
  • Better connection pooling management
  • More robust HTTP/2 handling
  • Improved keep-alive and compression settings

The changes follow Go best practices for HTTP client configuration and improve the overall robustness of the API client.

Testing:
I have:

  • Updated existing tests to use the new client configuration
  • Verified all tests pass with the new settings
  • Tested the changes with various network conditions
  • Ensured backward compatibility is maintained

Documentation:
I have:

  • Added clear comments explaining the configuration choices
  • Updated package documentation to reflect security considerations
  • Added inline documentation for timeout values and their purposes
**Original Pull Request:** https://github.com/ollama/ollama/pull/10813 **State:** open **Merged:** No --- This changes Ollama to use more secure and robust HTTP client configurations in the API package. The changes include: - Improved timeout configurations for better reliability - Enhanced transport security settings - Better connection pooling management - More robust HTTP/2 handling - Improved keep-alive and compression settings The changes follow Go best practices for HTTP client configuration and improve the overall robustness of the API client. **Testing:** I have: - Updated existing tests to use the new client configuration - Verified all tests pass with the new settings - Tested the changes with various network conditions - Ensured backward compatibility is maintained **Documentation:** I have: - Added clear comments explaining the configuration choices - Updated package documentation to reflect security considerations - Added inline documentation for timeout values and their purposes
GiteaMirror added the pull-request label 2026-04-13 00:25:17 -05:00
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 pull-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#13373
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?