Expand description
Reverse proxy admin support.
Provides a small registry that holds a handle to each running
ReverseServer so the admin HTTP server can expose live reverse
state (active control channels, active external streams,
bind-denied counters, dropped-stream counters) at /-/reverse.
The registry is intentionally lightweight: the runtime inserts a
handle per reverse server at startup, and admin reads snapshot
values directly from the underlying Arc<ReverseServerState>.
Structs§
- Reverse
Registry - Thread-safe registry of reverse servers. The runtime inserts a handle per server at startup; the admin route reads snapshots.
- Reverse
Server Entry - One reverse server entry — its identity and a handle to its state.
- Reverse
Server Entry Snapshot - Plain-data snapshot for the admin endpoint.
- Reverse
Server Id - Identifier for a reverse server. This is the user-supplied
id = "..."from the[[reverse_servers]]TOML block.