Hi,

I hope you took the second patch.
I tested this using the curl cli, and would be glad if you could too.

curl --interface 10.0.110.131 --local-port 60027-60028
https://10.20.4.19/cgi-bin/TEST/TEST.py

Would match your query.

As I do not have 10.20.4.19 here, here is a slightly different output
when asking for curl.haxx.se.

/opt/curl/bin/curl --verbose --interface 192.168.53.20 --local-port
41022-41023 http://curl.haxx.se > /dev/null
* About to connect() to curl.haxx.se port 80 (#0)
* Trying 91.191.140.28... Domain 192.168.53.20 is ip 192.168.53.20
* Local port: 41022
* connected
* Connected to curl.haxx.se (91.191.140.28) port 80 (#0)
...
works

If I take your output correct, "10.0.110.131" was not 'resolved' to an
ip address correctly.

> CURL: Trying 10.20.4.19... CURL: Domain 10.0.110.131 is ip

that line should look like:

"CURL: Trying 10.20.4.19... CURL: Domain 10.0.110.131 is ip 10.0.110.131"

Maybe Daniel can tell help me out on Curl_resolv and Curl_resolv_unlock?
Curl_resolv returns, h is not NULL, but the result is empty string?
Which resolver do you use?

Additionally, please try

curl --interface eth0 --local-port 60027-60028
https://10.20.4.19/cgi-bin/TEST/TEST.py

and replace eth0 by your interface

as well as

curl --interface myhostname --local-port 60027-60028
https://10.20.4.19/cgi-bin/TEST/TEST.py

and replace the hostname with your hostname.

and include the output with your mail.

MfG
Markus
Received on 2009-02-21