On Tue, 2019-09-17 at 16:08 +0200, Daniel Stenberg wrote:
> On Fri, 13 Sep 2019, David Woodhouse via curl-library wrote:
>
> > So: what would it take to use curl for HTTP while basically abusing it from
> > both sides? Not only do I need it to use my own underlying TLS connection,
> > but I also
On Fri, 13 Sep 2019, David Woodhouse via curl-library wrote:
So: what would it take to use curl for HTTP while basically abusing it from
both sides? Not only do I need it to use my own underlying TLS connection,
but I also need in some cases to make a CONNECT or even GET request which
complete
OpenConnect¹ is a SSL VPN client. It needs quite fine-grained control
over the TLS connection that it makes to the VPN server, to allow for
client certificates from various sources (TPM, PKCS#11, etc.) as well
as for interoperability reasons.
I didn't want to have to write my own HTTP support, but
