Skip to content

fix: force HTTP/1.1 for LLM API requests #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
efecnc wants to merge 3 commits into from
Closed

fix: force HTTP/1.1 for LLM API requests #22

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d046280
fix: force HTTP/1.1 for LLM API requests
efecnc May 6, 2026
096f442
Update src/utils.rs
efecnc May 6, 2026
1849e8e
fix: apply HTTP/1.1 only to DeepSeek, not all providers
efecnc May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/utils.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -330,6 +330,7 @@ pub struct LLMClient {
pub fn build_reqwest_client() -> reqwest::Client {
reqwest::Client::builder()
.no_proxy()
.http1_only()
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The PR description's assumption that the Anthropic provider uses a separate client path and is unaffected is incorrect; AnthropicProvider in src/provider.rs (line 92) calls this build_reqwest_client() function. Consequently, this change forces HTTP/1.1 for Anthropic as well, which contradicts the stated test plan and indicates that this provider may not have been verified with the protocol change.

Comment thread
efecnc marked this conversation as resolved.
.build()
.expect("failed to build reqwest client")
}
Expand Down