Implement a cURL stream #3183

cURL has a mode in which it acts a lot like our streams, providing send and recv functions and taking care of the TLS and proxy setup for us. Implement a new stream which uses libcurl instead of raw sockets or the TLS libraries directly. This version does not support reporting certificates or proxies yet.

If the stream claims to support this feature, we can let the transport set the proxy. We also set HTTPPROXYTUNNEL option so curl can create a tunnel through the proxy which lets us create our own TLS session (if needed).

Of the built-in ones, only cURL support it, but there's no reason a user-provided stream wouldn't support it.

The information is exposed by curl for some crypto libraries in the form of name:content strings. We can't do much more than return this information.

When linking against libcurl, use it as the underlying transport instead of straight sockets. We can't quite just give over the file descriptor, as curl puts it into non-blocking mode, so we build a custom BIO so OpenSSL sends the data through our stream, be it the socket or curl streams.

The TLS streams talk over the curl stream themselves, so we don't need to ask for it explicitly. Do so in the case of the non-encrypted one so we can still make use proxies in that case.

We do not want libcurl to perform the TLS negotiation for us, so we don't need to pass this option.

If the libcurl stream is available, use that as the underlying stream instead of the socket stream. This allows us to set a proxy for HTTPS connections.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Implement a cURL stream #3183

Implement a cURL stream #3183

Commits on Jun 24, 2015