Bugs item #1556186, was opened at 2006-09-11 10:24
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1556186&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: https
Group: wrong behaviour
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Daniel Stenberg (bagder)
Summary: socks5 and https

Initial Comment:
I try to connect to https hosts thru SOCKS5 proxy.
It's seems libcurl make mistake in this case. If I set
CURLOPT_PROXYPORT in (for example) 12345, then curl
try connect to remote 12345 port thru SOCKS5 proxy.

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2006-09-20 13:50

Message:
Logged In: YES
user_id=1110

Any news?

On what port do you run the SOCKS proxy? Are you saying it
connects to the same port on the proxy as on the remote host?

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-09-11 14:18

Message:
Logged In: NO

I produce this bug with next proxies:

12.218.168.177:16176
68.112.10.80:19955

but for now I can't connect to. I try to connect later.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-09-11 14:09

Message:
Logged In: NO

BTW, free SOCKS proxy list:

http://www.checker.freeproxy.ru/checker/
last_checked_proxies.php

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-09-11 14:02

Message:
Logged In: NO

Yes, I understand. I try to produce this bug again and take
curl log or something for you.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2006-09-11 13:51

Message:
Logged In: YES
user_id=1110

I guess I don't make myself clear. You still lack lots of
details and I don't understand what to fix.

I don't have any SOCKS* proxy around.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-09-11 13:48

Message:
Logged In: NO

This error occures only if I use SOCKS5 proxy. In case of
using HTTPS proxy (CONNECT method) all wents ok.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2006-09-11 13:44

Message:
Logged In: YES
user_id=1110

So _use_ the command line utilty then to get the trace!

Or use CURLOPT_VERBOSE or CURLOPT_DEBUGFUNTION to produce
such a trace.

I just find your description of the problem a bit lacking of
details so it would help us understand the problem.

Of course, even better would be if you produce a patch! ;-)

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2006-09-11 13:42

Message:
Logged In: NO

I use lubcurl 7.15.3 but not curl command line utility.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2006-09-11 10:26

Message:
Logged In: YES
user_id=1110

What curl version?

Can you please show us a full trace with --trace-ascii or at
least -v?

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1556186&group_id=976
Received on 2006-09-20