[Libwebsockets] [libwebsockets] SSL_connect on iOS with http proxy fails when SSL_connect can't connect immediately (with blocking sockets, branched from 6c58228) (#18)

"Andy Green (林安廸)" andy at warmcat.com
Fri Oct 25 16:11:01 CEST 2013

On 25/10/13 20:29, the mail apparently from shyswork included:
> Ok. It seems I've figured out what causes this problem. It is because of
> proxy and incorrect proxy handling with nonblocking sockets. Since
> __libwebsocket_client_connect_2 is called multiple times and the first
> time it overrides path to connect. That is why when we come back in
> __libwebsocket_client_connect_2 second time it tries to connect thru
> proxy again but with overridden address. That address is a proxy address
> itself. It connects and of course then it fails to establish SSL
> connection because proxy doesn't support that.

I think I see.... can you take a look at


and see if it matches your understanding?


>> Reply to this email directly or view it on GitHub
> <https://github.com/warmcat/libwebsockets/issues/18#issuecomment-27086619>.

More information about the Libwebsockets mailing list