Immutable TLS / mTLS material handed to the libcurl transport factory.
Strict server verification is ALWAYS on (§6); these fields only add a custom CA to the trust chain and/or present a client identity certificate (§6.1).
| unsigned axiam::TlsConfig::max_concurrent_requests = 16 |
Maximum libcurl easy handles the transport keeps, i.e.
the number of requests it can genuinely have in flight at once.
Before this existed the transport owned exactly ONE easy handle behind a mutex, so every call from every thread serialized — a client used concurrently had a p95 dominated by lock queueing rather than by the server. Set this to your application's expected concurrency; callers beyond it wait for a handle rather than opening an unbounded number of connections.
Cookies, DNS and TLS session state are shared across the handles (via libcurl's CURLSH), so the session is one session no matter which handle serves a given request. Connections are NOT shared: each handle keeps its own hot connection, which is the point.
