Repository navigation
共享库 1.3.2：V2.4 SSE 解析与 403 拒绝诊断（不修改客户端身份） - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
针对 OpenCode Zen 网关在 HTTP 403 中明确返回
Detect Abuse Traffic的现状，本 PR 不伪装客户端身份、不修改 User-Agent/工具指纹、不自动更换代理或重试。先补齐目前 Python V2.4 具备但 Java 共享库缺失的安全响应处理。OpenCodeZenUpstreamDiagnostics：有界解析 403/429，准确区分ABUSE_REJECTED、普通FREE_TIER_REJECTED、FORBIDDEN、RATE_LIMITED。OpenCodeZenSseEventReader：增量解析 SSE、命名事件、跨缓冲区 UTF-8、多行data:、[DONE]、上游错误和 32MiB 限制。1.3.2（尚未发布 Maven 包），新增说明。验证边界
HTTP 200
/models是发现模型，不代表推理已获准。Provider 403Detect Abuse Traffic为服务端访问控制信号，应停止连续请求并联系服务商，不能凭离线测试声称可调用。本 PR 不承诺实现 200 推理；CI 仅用于校验 Java 编译/测试。