Antonio Quartulli
Antonio Quartulli
Yeah, that makes sense. What I have in mind is some kind of common abstraction layer made up by a set of functions that are attached to a different implementation...
API has partly changed. Also some objects have to be handled differently. But axel does not use the SSL API that heavily..therefore it may also be that it will just...
[libtls](https://man.openbsd.org/tls_init) could be used as intermediate layer. It's a generic layer exposing a simple TLS API that is currently implemented by libreSSL and OpenSSL. porting to mbedtls should not be...
in my libtls branch it is possible to find a PoC for switching to libtls.
Apparently this is a wanted behaviour (somebody correct me if I am wrong), therefore I think this is more a feature request than a bug (?). Imho the tricky part...
yeah, that could be a good idea. if no flag is specified, then we spawn as many connections as the urls. If the flag is specified but the number is...
I am not sure if we do handle that correctly. we should check that
Can this really be achieved? HTTPS through proxy means we can't verify the final certificate, right? because it will be the proxy to do that for us.
Right, using connect CONNECT it makes sense
I think it would be much better to avoid adding other dependencies unless strictly required. Don't you think it is possible to implement basic socks support without a library?