We need the ability to customize how wreq caches TLS sessions. Right now the TLS stack uses a hardcoded…
We need the ability to customize how wreq caches TLS sessions. Right now the TLS stack uses a hardcoded…: a task in LegoFlow-SWE (Harbor dataset). We want to allow callers to provide their own TLS session cache through the public TLS configuration API. Once configured, the underlying TLS connector…
The task
We want to allow callers to provide their own TLS session cache through the public TLS configuration API. Once configured, the underlying TLS connector should use that cache for all session storage and retrieval, and session resumption should behave according to whatever caching strategy the user supplies.
Part of Lego-X/LegoFlow-SWE.