Skip to main content

Connection Lifecycle

A session isn't a one-shot object. It opens connections, caches tickets, accumulates cookies, hops protocols, gets persisted to disk, fans out into siblings. This section covers each operation that moves a session through those states without rebuilding it from scratch.

In this section​

  • Refresh: drop every live connection but keep tickets, cookies and fingerprint state, the way a browser tab reload works
  • Warmup: multi-hop browser-style preflight that fetches the page and its subresources before the real request
  • Protocol Switching: move between H1, H2 and H3 mid-session, with or without auto-negotiation
  • Session Save and Restore: serialize the whole session to JSON, load it back in another process
  • Fork: N sibling sessions sharing cookies and TLS state, each with its own connection pool
  • Observability: Stats, IdleTime, Touch, ClearCache, GetTransport for inspecting live session state