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).

[svrooij]

@harrison314 do you need any https inspection? Or can it run on its own https certificate? Anyway in the rewrite there is an interface that is called to create the http client for the back channel communication for some host. It will get the hostname and you can return your own http client.

So as long as you can construct a http client that can handle the back channel communication you should be good with the new code.

Otherwise yarp might be a good alternative to check-out.