Expand description
The deliberately small wire adapter for pproxy 2.7.9 backward links.
pproxy’s ProxyBackward is not the native Eggress reverse protocol. A worker opens a transport to the remote listener, writes the configured auth bytes without a delimiter, and then waits for the remote listener to put that channel to work. Keeping this implementation separate is important: changing the native reverse handshake would change the native protocol.
Structs§
- Pproxy
Backward Client - A pproxy-compatible backward client. One instance owns exactly one persistent worker; callers create one instance per +in occurrence.
- Pproxy
Backward Client Config - Configuration for one pproxy backward worker.
- Pproxy
Backward Server - pproxy-compatible accepting side. It has no native handshake byte and never mutates the native ReverseServer.
- Pproxy
Backward Server Config - Configuration for the pproxy-compatible accepting side.
Enums§
- Pproxy
Backward Framing - Channel framing applied between the compatibility adapter and the
peer
pproxy 2.7.9process after the auth handshake completes. - Pproxy
Backward State - pproxy backward reconnect states, exposed for deterministic tests and diagnostics.
Functions§
- raw_
auth - Build the raw auth field used by pproxy’s ProxySimple.auth property.