Roadmap

路线图与非目标

明确划清边界有助于正确使用。以下为有意不做、安全拒绝或需显式开启的能力，以及未来改进方向。

明确的非目标

HTTP/1.1

• HTTP 管线化（串行请求/响应，刻意不实现）
• TRACE 方法
• 入站 request parser / server role
• obs-fold 折行（安全拒绝而非规范化）
• 调用方手写 Transfer-Encoding / TE（安全拒绝，framing 由库生成）

HTTP/2

• 发送 PRIORITY 帧（合法地省略）
• 后台自动 PING 保活策略（低层已提供显式 SendPing，不默认启动定时器）
• server push（客户端 ENABLE_PUSH=0，收到 PUSH_PROMISE 安全拒绝）

WebSocket（注：分片发送 kws::SendContinuation 与显式接收分片 ReceiveOptions.DeliverFragments=true 已支持）

• permessage-deflate（RFC 7692）
• 高层 kws 默认自动选择 WebSocket over HTTP/2（RFC 8441 已支持显式 opt-in，默认仍保持 HTTP/1.1 Upgrade）
• 握手 redirect / 401 / 407 跟随（当前安全拒绝为 STATUS_NOT_SUPPORTED；未来若做必须显式 opt-in）

TLS

• TLS 1.2 renegotiation（仅信令，未实现）
• 在线撤销抓取（OCSP/CRL 网络拉取）——内核态刻意省略，支持静态撤销条目

其它

• HTTP/3 / QUIC

默认关闭、可显式开启

• TLS 1.2 RSA key exchange / CBC / renegotiation / SHA-1 签名（需 TlsPolicy + CompatibilityExplicit）
• Post-handshake client auth
• 强制撤销检查
• TLS 1.3 0-RTT
• Expect: 100-continue（SendFlagExpectContinue + ExpectContinueTimeoutMs）
• 高层 h2c prior knowledge / Upgrade（SendOptions.Http2CleartextMode）
• WebSocket over HTTP/2（ConnectConfig.AllowWebSocketOverHttp2）

未来改进方向（持续）

• 继续扩展协议安全边界上的有界账本，例如更细的超时、取消、帧/控制信令与恶意输入防护；普通 buffered response 默认不设置低位库级总量硬顶。
• 继续减少热路径重复分配，优先复用 Workspace / lookaside / 连接生命周期常驻缓冲。
• 评估 WebSocket over HTTP/2 从显式 opt-in 走向自动选择的 API 与兼容性策略。
• 保持明文 HTTP over proxy 的 absolute-form 路径与 HTTPS CONNECT 隧道路径分离，继续审计代理鉴权 opaque 透传边界。

这些是对当前公开行为的描述，便于评估适用性；不代表内部审计细节。能力现状见 能力账本。

---

English

Roadmap & Non-Goals

Explicit boundaries help correct usage. The following are intentionally out of scope, security-rejected, or explicit opt-in, plus ongoing improvement directions.

Non-goals / security rejections. HTTP/1.1: pipelining, TRACE, inbound request parser/server role, obs-fold normalization (rejected), caller-supplied Transfer-Encoding/TE (rejected because the library owns framing). HTTP/2: PRIORITY frames, automatic background PING keepalive (explicit low-level SendPing exists), server push (ENABLE_PUSH=0; PUSH_PROMISE is rejected). WebSocket (fragment send + explicit ReceiveOptions.DeliverFragments receive-fragment delivery are supported): permessage-deflate (RFC 7692), automatic-by-default high-level WebSocket over HTTP/2 (RFC 8441 is available via explicit opt-in), handshake redirect/401/407 following (currently rejected with STATUS_NOT_SUPPORTED; any future support must be explicit opt-in). TLS: TLS 1.2 renegotiation (signaling only), online OCSP/CRL fetch (omitted in kernel; static entries supported). Other: HTTP/3·QUIC.

Off by default, explicitly enable. TLS 1.2 RSA kx / CBC / renegotiation / SHA-1 (via TlsPolicy + CompatibilityExplicit), post-handshake client auth, required revocation check, TLS 1.3 0-RTT, Expect: 100-continue (SendFlagExpectContinue), high-level h2c prior knowledge / Upgrade (SendOptions.Http2CleartextMode), and WebSocket over HTTP/2 (ConnectConfig.AllowWebSocketOverHttp2).

Future directions. Continue tightening protocol-safety ledgers such as timeouts, cancellation, frame/control-signal and malicious-input bounds while leaving normal buffered responses unlimited by default; reduce repeated allocations on hot paths via Workspace/lookaside/connection-resident buffers; evaluate moving WebSocket over HTTP/2 from explicit opt-in toward automatic selection with a compatibility plan; keep plaintext HTTP over proxy absolute-form separate from HTTPS CONNECT tunneling and continue auditing opaque proxy-auth forwarding.

This describes current public behavior for fit assessment; see Capability Matrix for the current state.