Ability to use your own socket as an HTTP client

[harrison314]

Is it possible to define a custom socket client for egress communication instead of an HTTP client in the proxy?

I have two use cases:

• I would need to create a proxy that translates HTTPS to unix domain sockets.
• I would like to create a proxy that authenticates to a remote server using mTLS. However, dotnet HttpClient can only use a client certificate in the MS cert store or a P12/pfx file. In my case, the certificate is stored either on a smart card or on a remote server (similar to Azure Key Vault).