- [Upstream HTTP/2 Protocol Hardening & Stream Drop Fix] Completely remove destructive HTTP/2 PING injection, restore native Chrome 123 protocol baseline, and eliminate 10s deep-thinking disconnects (Fixes #3593):
- Root Cause Elimination for Destructive HTTP/2 PING: Protocol frame tracing confirmed that Google GFE / Cloudcode endpoints silently drop client-initiated HTTP/2 PING frames without returning PING ACKs. In v4.8.9 (PR #3571), the configured
keep_alive_timeout = 10scaused local hyper2 to unilaterally terminate the connection at exactly 10s when waiting for an ACK, throwingerror reading a body from connection (buffer_bytes=0). The destructive.http2(|mut h2| ...)configuration has been completely removed fromUpstreamClient, eliminating the local self-abort timer. - Restoration of Native Chrome 123 Behavior & L4 Keep-Alive: Strictly aligned with real Chrome 123 browser protocol behavior (browsers never send HTTP/2 PING frames at the application layer), relying on standard L4 TCP Keep-Alive (60s). Seamlessly collaborates with PR #3578's downstream SSE 3s comment heartbeats (
: ping\n\n) to prevent client-side idle timeouts without jeopardizing upstream stability. - Eliminate Connection Pool Pollution & 503 Token Pool Exhaustion: Removed idle PINGs from
keep_alive_while_idle(true)that poisoned pooled connections, resolving the failure on consecutive requests and preventing cascading account lockouts that led to503 Token pool is empty. - Deep Stress Testing Verification: Rigorously verified with long-generation benchmarks; models successfully sustained over 15.30s of initial silent thinking pauses and generated over 250KB across 125s+ with 100% connection reuse success.
- Root Cause Elimination for Destructive HTTP/2 PING: Protocol frame tracing confirmed that Google GFE / Cloudcode endpoints silently drop client-initiated HTTP/2 PING frames without returning PING ACKs. In v4.8.9 (PR #3571), the configured
- [上游底层 HTTP/2 协议栈重构与根治假死断流] 彻底移除破坏性 HTTP/2 PING 注入，回归真实 Chrome 123 原生协议基线，终结深度思考与长上下文 10s 自杀式断流 (Fixes #3593):
- 根因溯源与彻底移除有毒 HTTP/2 PING: 深入抓包与底层协议状态机实测证实，Google GFE / Cloudcode 生产端点对客户端主动发送的 HTTP/2 PING 帧静默丢弃、100% 不回复 PING ACK。v4.8.9 (PR #3571) 配置的
keep_alive_timeout = 10s导致本地 hyper2 在思考静默期等不到 ACK 时于第 10 秒整准时在客户端本地主动杀死连接，抛出error reading a body from connection (buffer_bytes=0)。现彻底移除UpstreamClient中破坏性的.http2(|mut h2| ...)配置，拔除本地等待 ACK 的自杀定时炸弹。 - 回归 Chrome 123 原生协议行为与稳态 L4 保活: 严格对齐真实 Chrome 123 浏览器的协议行为（真实浏览器在 HTTP/2 层从不发应用层 PING），完全依赖操作系统的标准 L4 TCP Keep-Alive (60s)；同时与 PR #3578 在下游 SSE 提供的 3s 纯文本注释心跳（
: ping\n\n）形成完美协同，既防止下游客户端/IDE 空闲超时，又保证上游长思考连接绝不断流。 - 消除空闲连接池污染与根除 503 Token pool is empty 雪崩: 彻底清除后台
keep_alive_while_idle(true)对连接池空闲连接乱发得不到 ACK 的 PING 所造成的连接坏死，消灭“连续请求两次就失败”的连接复用崩溃，避免网关因连接断开误触发重试熔断将可用账号锁死，彻底解决账号池雪崩问题。 - 超长任务与长思考深度压测验证: 经真实凭据长任务压测，模型在经历长达 15.30 秒的首包思考完全静默期依然稳如磐石，连续跑满 125 秒（25 万字节）大生成且多轮连接池复用 100% 成功，连接零断流。
- 根因溯源与彻底移除有毒 HTTP/2 PING: 深入抓包与底层协议状态机实测证实，Google GFE / Cloudcode 生产端点对客户端主动发送的 HTTP/2 PING 帧静默丢弃、100% 不回复 PING ACK。v4.8.9 (PR #3571) 配置的
What's Changed
- fix(proxy): 修复 Claude 5.5 原始 Protobuf 思考签名识别与出站格式校验 by @cubelikeplayDaniel in #3595
Full Changelog: v4.9.2-beta.8...v4.9.2-beta.9