Expand description
[proxy] — which forward proxy, if any, an outbound connection goes
through.
The policy half of outbound HTTP, the way crate::http_client is the
plumbing half: that module’s own doc says it “owns the plumbing and nothing
else”, and selection is not plumbing. It is an environment fallback with a
documented precedence, six matching rules, a startup vocabulary of refusals
and a credential that must never reach a log.
Reaching into crate::filter for [parse_net]/[canonical] is a choice,
not an accident: that subsystem is inbound policy and this is outbound, but
CIDR parsing is CIDR parsing, and two of them would drift. If a third
consumer ever appears, hoist those four helpers into a neutral module rather
than growing a second copy here.
Structs§
- Outbound
Proxies - The process-wide outbound proxy configuration, resolved once at startup.
- Proxy
Target - One proxy, already picked apart.
Functions§
- from_
config - Builds the process’s proxy configuration, wrapped for the subsystems that each keep a clone.