TLS session-resumption cache is lost when a listener is recreated (cache is per-proxy, not per-process)

未关闭
#58 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
networking

调研方向

Start in src/proxy.rs at the TlsConfigCache construction near line 443, then check how src/suspended.rs near line 122 creates a fresh cache per connection. The open question is who owns the cache's lifetime and when entries are swept, so settle that with the maintainers before editing. Done means a listener recreate keeps resumption working for a rotated-certificate case without reusing stale entries.

由索引模型根据 Issue 内容生成。

描述

TlsConfigCache is created per SymphonyProxy (src/proxy.rs:443, main 222a442). When the embedding server recreates a listener because its signature changed (for example, a listener certificate rotation), the new proxy starts with an empty cache. Every client on that port then does a full handshake instead of resuming.

Cert renewal is the most common reason for a recreate, so the deployment path that rotates certificates is the one that loses resumption.

Fix shape: hoist the cache to process scope (or let the embedder pass one in), keyed so entries tied to a rotated certificate are invalidated rather than reused. This needs a decision on who owns the cache's lifetime and when entries are swept.

(Related, queued separately: resolved/suspended routes create a fresh cache per connection, src/suspended.rs:122.)

Found during finding-triage wave 29. — Claude Opus 5.5

主要语言
TypeScript
星标
1
派生
0
平均合并
11 小时 49 分钟
30 天内合并 PR
12

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

HarperFast/symphony 的其他 Issue

查看 HarperFast/symphony 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。