Expand description
Read git’s http.<key> and http.<url>.<key> settings.
Mirrors the small subset upstream consults when wiring TLS into its
HTTP client. URL-specific overrides (http.<url>.<key>) are
resolved by longest prefix match against the request URL, the same
way git itself routes them.
Only a few keys are surfaced for now (CA bundle, verify toggle, and
the client-cert pair for mTLS); the rest of the surface
(sslCertPasswordProtected, cookieFile, …) is on the deferred
list.