Struct ptproxy::config::SystemConfig
source · pub struct SystemConfig {
pub connect_interval: Option<u64>,
pub tcp_nodelay: Option<bool>,
pub wait_for_first_attempt: Option<bool>,
pub watchdog_factor: Option<f32>,
pub add_forwarded: Option<bool>,
}
Expand description
Limits, timeouts, intervals and other parameters that affect operation of ptproxy. This includes proxy behavior, integration with the service manager, and interaction with HTTP/1.1 upstreams / downstreams.
Fields§
§connect_interval: Option<u64>
Time to wait since last QUIC connection [attempt] failed before attempting a new connection, in milliseconds.
Only used in client mode.
Default: 1000
tcp_nodelay: Option<bool>
Whether to enable the TCP_NODELAY
option on incoming (client mode) or outgoing (server mode) HTTP/1.1 sockets.
This helps avoid extra latency introduced by delayed ACKs, for example.
Default: true
wait_for_first_attempt: Option<bool>
If enabled and service manager integration is in use, ptproxy will wait for the first connection attempt
to finish (successfully or not) before sending signalling the service as ready. This gives a best-effort
opportunity for the tunnel to establish before starting dependencies, for example.
Only used in client mode.
Default: true
watchdog_factor: Option<f32>
If service manager integration is in use, and this service has been requested to send periodic keepalives,
the watchdog timeout limit is divided by this factor to determine the interval at which to send them.
Default: 1.5
add_forwarded: Option<bool>
If enabled, a Forwarded
header will be appended to the request before forwarding it.
Default: false