TLS session-resumption cache is lost when a listener is recreated (cache is per-proxy, not per-process)
维护者通常 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 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
HarperFast/symphony 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
HarperFast/symphony#91 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
HarperFast/symphony#89 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 49/100
HarperFast/symphony#93 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
HarperFast/symphony#92 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 72/100
HarperFast/symphony#90 ·
维护者通常 1 天内回复
查看 HarperFast/symphony 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
feature request needs triage
难度 1/5 1-3 小时 新手友好度 69/100
-
难度 2/5 1-3 小时 新手友好度 82/100
solidjs/solid-docs#1716 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 80/100
thecodacus/pithagoras#380 ·
维护者通常 1 天内回复