fix the Curl_connected_proxy function for when libcurl actually connects fine
to it in the actual connect call and not asynchronously.
This commit is contained in:
Родитель
e6e6c6e635
Коммит
f04720afb8
|
@ -2825,6 +2825,12 @@ CURLcode Curl_connected_proxy(struct connectdata *conn)
|
||||||
CURLcode result = CURLE_OK;
|
CURLcode result = CURLE_OK;
|
||||||
struct SessionHandle *data = conn->data;
|
struct SessionHandle *data = conn->data;
|
||||||
|
|
||||||
|
if(conn->bits.tcpconnect)
|
||||||
|
/* allow this to get called again from the multi interface when TCP is
|
||||||
|
found connected in the state machine, even though it has already been
|
||||||
|
called if the connection happened "instantly" */
|
||||||
|
return CURLE_OK;
|
||||||
|
|
||||||
switch(data->set.proxytype) {
|
switch(data->set.proxytype) {
|
||||||
#ifndef CURL_DISABLE_PROXY
|
#ifndef CURL_DISABLE_PROXY
|
||||||
case CURLPROXY_SOCKS5:
|
case CURLPROXY_SOCKS5:
|
||||||
|
|
Загрузка…
Ссылка в новой задаче