Expand description
L4 (TCP/UDP) stream proxying — a data path independent of the HTTP engine.
Each configured StreamListenerConfig binds a port at startup and relays
raw bytes to an upstream pool selected by the shared Balancer. There is
no Context, no node-graph, and no per-request matching: a listener maps a
port straight to a backend pool. TCP uses copy_bidirectional; UDP tracks
per-client sessions (see tcp and udp).
Modules§
- sni 🔒
- SNI-based routing for TCP TLS passthrough.
- tcp 🔒
- TCP stream proxy: accept a client, pick a load-balanced upstream (optionally by TLS SNI), and relay bytes in both directions until either side closes.
- udp 🔒
- UDP stream proxy: relay datagrams between clients and a load-balanced upstream, tracking one session per client address.
Functions§
- start_
all - Binds every configured stream listener and spawns its accept/receive loop.