On Monday 02 February 2004 17:04, Daniel Stenberg wrote:
> > And error messages while using http proxy are misleading. "Could not
> > resolve host" and "Could not connect" can apear for the proxy and the
> > web host. I hope I find the time to fix it this week.
>
> I'm not following you here. How are they misleading?

Non-ares curl-7.11.0-20040123:

  $ ./curl --proxy blah:9999 http://127.0.0.1/
  curl: (5) Couldn't resolve proxy 'blah'

Thats ok, but

  $ ./curl --proxy localhost:9999 http://127.0.0.1/
  curl: (7) Connect failed

should be "Could not connect proxy".

Ares version:

  $ ./curl --proxy blah:9999 http://127.0.0.1/
  curl: (6) Could not resolve host: 127.0.0.1

Uh, wrong messsage.

  ./curl --proxy localhost:9999 http://127.0.0.1/
  curl: (7) Connect failed

Same as non-ares.

Greetings,
Dirk

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
Received on 2004-02-03