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

Open
#58 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
networking

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
11h 49m
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HarperFast/symphony

All issues in HarperFast/symphony

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.