Hello!

No I do not think it is enough.
This is the verbose output from curl command:
* About to connect() to proxy my.proxy.se port 8080 (#0)
* Trying 153.88.253.11... connected
* Connected to my.proxy.se (153.88.253.11) port 8080 (#0)

As you can see I can connect via the curl command but not via the API.
This is strange and my only guess is that the fault is in building the
libcurl.

What does 'curl -x my.proxy.se:8080 www.google.se' do API wise?
Is it only:
curl_easy_setopt(curl, CURLOPT_PROXY, "my.proxy.se:8080");
curl_easy_setopt(curl, CURLOPT_URL, "www.google.se");
res = curl_easy_perform(curl);
curl_easy_cleanup(curl);

BR
Robert

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Daniel Stenberg
Sent: den 17 oktober 2008 09:53
To: libcurl development
Subject: RE: curl binary OK libcurl NOK

On Fri, 17 Oct 2008, Robert Thorhuus wrote:

> * About to connect() to proxy my.proxy.se port 8080 (#0)
> * Trying 153.88.253.11... * Failed to connect to 153.88.253.11:
Error
> 0
> * Error 0
> * couldn't connect to host

Isn't this description enough? libcurl fails to connect to TCP port 8080
of the IP address the proxy name resolves to.

("Error 0" looks a bit strange though!)

If you use 'curl -v' and compare the curl tool's output, does it show
any diff that explains anything?

-- 
  / daniel.haxx.se