>
> I want my program to be fault tolerant to certain errors, so I intercept
>> the CURL_COULDNT_CONNECT error and reset the handle. I would like to know
>> why my program cannot recover from this error after doing a
>> curl_easy_duphandle. I am able to connect to the server outside of my
>> progra
"Yang Tse" wrote:
I have no clue. Around here I only have VC6 and msvc makefile/projects
provided with lwIP 1.4.0 only support newer msvc compilers. :-(
I found the LwIP netif files in an extra distro; installed under
'src/contrib/ports/win32'. I managed to build it and link to curl okay,
b
>That seems very odd. When libcurl has a proxy to use, it doesn't matter how it
>got it, it will stilll use the proxy the same way.
It seems that curl don't know there is proxy setting in https_proxy. ( socks
proxy and http proxy are all the same)jelly@jelly-PC2 ~/test-zip-git-clone
$ echo $https
On Tue, 2 Aug 2011, Christian Hägele wrote:
I don't see any reason against calling Curl_inet_pton before starting a new
thread to check if we already have a dotted IP. Thats the same what already
happens in the asyn-ares.c solution. I have a patch against the nightly
build of august 2nd attach
On Sat, 6 Aug 2011, jelly wrote:
i can run "curl --socks5 localhost:9050 https://code.google.com/p/wiztodo
-k" successful.i can use git with socks proxy in http.proxy
...
But i run these commands fail, seems curl and git can not use
socks proxy settings in https_proxy:
That seems very odd.
