0.6.13:网关错误诊断与发送失败回归
- 区分 Gateway 入站请求接收超时(408
request_timeout)、请求头过大(431headers_too_large)和其他非法 HTTP 请求(400bad_request)。现有超时、请求体限制、认证、CSRF 和单次 POST 转发策略保持不变。 - 新增隐私受限、按网关采样的 HTTP 拒绝诊断,区分解析失败、非法目标和已认证的上游
POST /api/session/prompt拒绝。日志不记录正文、Cookie、Token、原始数据包、任意 URL 或查询参数。 - 补齐 LAN、自有反代、普通远程和自签 FRP 四种 Gateway 工厂的诊断接线,并补充真实 HTTP 组合回归。
- 新增打包 DSH 0.2.0-rc.2/0.2.1-rc.2 的文字与图片 400 失败恢复检查:验证草稿、图片和原生错误提示恢复,确认不会自动重发或触发 Host/模型请求。
- DSH 源码和已安装前端保持只读。发送中切换会话导致的恢复状态丢失已在纯 DSH 对照中复现,属于上游生命周期问题,不由本插件伪修。
Android App 仍为 0.6.5 / build 81,不需要同步升级。#235 的 iroh P2P 方案不属于本版本,也不会进入 dsh-mobile 主仓库;独立概念验证另行维护。
English
- Distinguish Gateway inbound receive timeouts (408
request_timeout), oversized headers (431headers_too_large) and other malformed HTTP requests (400bad_request), while retaining existing limits, authentication, CSRF and single-attempt POST forwarding. - Add privacy-bounded per-Gateway HTTP rejection diagnostics for parser failures, invalid targets and authenticated upstream
POST /api/session/promptrejections. Bodies, Cookies, Tokens, raw packets, arbitrary URLs and queries are excluded. - Cover all four Gateway factories with real HTTP diagnostic composition checks.
- Add packed DSH 0.2.0-rc.2/0.2.1-rc.2 text and image 400 recovery checks for restored drafts, images and visible stock errors, with no automatic replay or Host/model request.
- DSH source and installed frontend artifacts remain read-only. Pending-send navigation recovery loss is reproduced in pure stock DSH and remains an upstream lifecycle issue, not a plugin workaround.
Android App 0.6.5 / build 81 is unchanged. The proposed iroh P2P channel in #235 is outside this release and remains an independent concept-validation project.