"Daniel Stenberg" <daniel-curl_at_haxx.se> said:

> > It would be nice if libcurl could tell us all the IP it tried and the result
> > of each failed attempt.
>
> I think I agree. You have any patch doing this?

I've started work on this. But how should CURLOPT_CONNECTTIME
be interpreted? Max-time on each connection or max-time for all the
IP tried?

If I do 'curl -vc2 http://ubr4-ca5-0-sec.landg1.lb.home.nl', this takes
47sec for the 7 IPs tried. Much more than 2sec per IP.

Wheras 'curl -vc2 ftp://ubr4-ca5-0-sec.landg1.lb.home.nl' gives up
after 1 sec?!

* About to connect() to ubr4-ca5-0-sec.landg1.lb.home.nl port 21
* Connected to ubr4-ca5-0-sec.landg1.lb.home.nl (82.73.204.1) port 21
* FTP response reading failed
* Closing connection #0
curl: (56) FTP response reading failed

I've spoke about this before; the above is completely untrue. tcpdump
shows I receive a RST for each of my SYNs. So no way I'm connected.
The host has no ftp nor http-servers so I'd expect ftp to behave like http
connect.

--gv
Received on 2004-06-09