Provide common way to specify cert overrides
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 998
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
Thanks for such a cool and useful tool! I'm not sure if this is in scope of the project, but I just started using llm with gemini on a company computer that has self-signed certificates. I had to dig into the implementation of llm-gemini to see that it was using httpx, then figure out how to override the SSL chain for that library.
It might be too niche of a use-case, but I could see value in having a more global override, since I believe some plugins may need a different way to specify the trusted cert, depending on implementation.
References:
https://www.python-httpx.org/environment_variables/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the llm-gemini plugin configures httpx and review the HTTPX environment-variable reference linked in the issue. Done should mean users have one documented certificate override that can work consistently across plugins with differing HTTP clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100