Expand description
Requests this node makes to services an administrator configured.
Inbound HTTP serving remains the responsibility of each application. Both admission and lifecycle hooks talk to operator-supplied endpoints, and they share exactly this much: a pooled connection, bounded time, a bounded response, and a bearer credential. What they do with the answer is entirely different — admission fails closed and never retries, hooks queue and retry — so none of that is here.
Two properties come from what is not enabled rather than from code, and
both are load-bearing. hyper-util’s client does not follow redirects, so a
bearer token can never be replayed to another origin by a redirecting
endpoint. Its client-proxy feature is off, so no environment variable can
silently route these requests through a third party.
Cleartext endpoints are permitted. Whether a hop is protected is not
knowable from the URL — a service mesh or a private network may be doing it
— so Endpoint::is_encrypted reports the scheme and leaves the judgement
to the operator who chose the address.
Structs§
- Bearer
Token - A bearer credential, kept out of anything that prints.
- Client
Config - Client
Tls - Loaded outbound TLS material, holding its own rotation watch.
- Client
TlsFiles - The paths one destination configures; all optional.
- Endpoint
- A validated destination.
- Http
Client - A pooled HTTP client shared by everything that calls out.
- Invalid
Token - Lazy
Http Client - Builds at most one outbound client, and only if something needs it.
- Response
- What an endpoint answered.
Enums§
- Client
TlsError - Why a destination’s TLS material is unusable.
- Endpoint
Error - Outbound
Error