There are two asynchronous name resolutions at the same time (Proxy and
destination server) and only one wait....

I didn't see a way to differentiate which name failed in an async
lookup.

Any suggestions where to look?

Brad

-----------------------------------------------------
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced
-----------------------------------------------------
 
-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Bradford Bruce
Sent: Thursday, October 20, 2005 5:30 PM
To: libcurl development
Subject: RE: Name resolution under Windows

I'll try it tomorrow, but I don't think so.

This is the only place where the invalid proxy error is set.

I'll look for somewhere else where this condition can be set, but I'm
not completly familiar with the code yet.

Brad

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se on behalf of Daniel Stenberg
Sent: Thu 10/20/2005 4:35 PM
To: libcurl development
Subject: RE: Name resolution under Windows
 
On Thu, 20 Oct 2005, Bradford Bruce wrote:

> This is the first time I've submitted a change, so I hope this works.

It might work for your particular case, but the url.c change breaks the
multi
interface miserably for proxy-using cases... There is a reason for
Curl_wait_for_resolv() not being used already. It is meant to be allowed
to
happen asynchronously...

Doesn't the hostthre.c change alone fix the problem?

-- 
  Commercial curl and libcurl Technical Support:
http://haxx.se/curl.html
NOTICE: This e-mail and any attachment may contain confidential and/or legally privileged information. If you are not the intended recipient, you must not review, retransmit, print, copy, use or disseminate it. Please immediately notify us by return e-mail and delete it along with any attachment and do not retain a copy. If this e-mail contains a forwarded e-mail or is a reply to a prior e-mail, the contents may not have been produced by the sender and therefore we are not responsible for its contents.
This notice is automatically appended to each e-mail. It is the recipient's responsibility to take measures to ensure that this e-mail is virus free, and no responsibility is accepted by us for any loss or damage arising in any way from its use.