Module https_service
dns and http and std only.Expand description
HTTPS DNS knowledge for the existing HTTP service selector.
Compose this before HttpServiceConnector, proxy selection and pooling.
Discovery changes connection candidates, never the logical origin. DNS
caching belongs to the supplied resolver. Named-proxy discovery is opt-in;
even when enabled it never starts local destination address lookups.
HTTPS DNS + Alt-Svc -> candidates + per-candidate extensions
|
select candidate <---+ failure, if allowed
| |
proxy route |
| |
pool lookup |
/ \ |
hit miss |
| | |
| connect + TLS ---+
| | success
+----> use connectionPool lookup uses the selected candidate’s endpoint and policy. Custom preknowledge producers can supply the same candidates and extensions.
Use the same TLS defaults and Alt-Svc cache in discovery and selection.
WebSocket (wss) service selection and HTTP-to-HTTPS upgrades are not
implemented by this layer. Each Alt-Svc authority has independent ECH
reliance, as specified by RFC 9848 section 6: an origin’s ECH advertisement
does not itself require its separately advertised alternatives to offer ECH.
Custom resolvers reuse the same interpretation and extension contracts. See
the http_https_discovery_custom_resolver and http_ech_preknowledge examples.
DNS-free producers can supply candidate-local facts directly. Apply caller
ECH intent and EchRequirement::Required separately on the request; the
backend checks acceptance on new connections and pooled reuse.
Structs§
- Https
Service - Inject DNS-derived candidate knowledge before invoking the inner connector.
- Https
Service Layer - Reusable HTTPS discovery configuration, independent of an easy client.