I tested only curl, it reports Proxy CONNECT aborted.

jelly_at_jelly-PC2 ~
$ echo $http_proxy

jelly_at_jelly-PC2 ~
$ curl https://code.google.com/p/wiztodo
curl: (35) Unknown SSL protocol error in connection to code.google.com:443

jelly_at_jelly-PC2 ~
$ export http_proxy=localhost:9050

jelly_at_jelly-PC2 ~
$ echo $http_proxy
localhost:9050

jelly_at_jelly-PC2 ~
$ export https_proxy=localhost:9050

jelly_at_jelly-PC2 ~
$ echo $https_proxy
localhost:9050

jelly_at_jelly-PC2 ~
$ curl https://code.google.com/p/wiztodo
curl: (56) Proxy CONNECT aborted

jelly_at_jelly-PC2 ~
$ curl https://code.google.com/p/wiztodo -vvv
* About to connect() to proxy localhost port 9050 (#0)
* Trying ::1... connected
* Connected to localhost (::1) port 9050 (#0)
* Establish HTTP proxy tunnel to code.google.com:443
> CONNECT code.google.com:443 HTTP/1.1
> Host: code.google.com:443
> User-Agent: curl/7.20.1 (i686-pc-cygwin) libcurl/7.20.1 OpenSSL/0.9.8r zlib/1.
2.5 libidn/1.18 libssh2/1.2.5
> Proxy-Connection: Keep-Alive
>
* Proxy CONNECT aborted
* Closing connection #0
curl: (56) Proxy CONNECT aborted

jelly_at_jelly-PC2 ~
$ which curl
/usr/bin/curl

jelly_at_jelly-PC2 ~
$ curl https://code.google.com/p/wiztodo -vvv
* About to connect() to proxy localhost port 9050 (#0)
* Trying ::1... connected
* Connected to localhost (::1) port 9050 (#0)
* Establish HTTP proxy tunnel to code.google.com:443
> CONNECT code.google.com:443 HTTP/1.1
> Host: code.google.com:443
> User-Agent: curl/7.21.8-DEV (i686-pc-cygwin) libcurl/7.20.1 OpenSSL/0.9.8r zli
b/1.2.5 libidn/1.18 libssh2/1.2.5
> Proxy-Connection: Keep-Alive
>
* Proxy CONNECT aborted
* Closing connection #0
curl: (56) Proxy CONNECT aborted

jelly_at_jelly-PC2 ~
$ curl --version
curl 7.21.8-DEV (i686-pc-cygwin) libcurl/7.20.1 OpenSSL/0.9.8r zlib/1.2.5 libidn
/1.18 libssh2/1.2.5
Protocols: dict file ftp ftps http https imap imaps pop3 pop3s rtsp scp sftp smt
p smtps telnet tftp
Features: IDN IPv6 Largefile NTLM SSL libz

jelly_at_jelly-PC2 ~
$
At 2011-08-04 05:43:48,"Daniel Stenberg" <daniel_at_haxx.se> wrote:
>On Tue, 2 Aug 2011, jelly wrote:
>
>> Thank you! I have updated my libcurl to the latest version, but still can
>> not use socks proxy.
>
>Ok, thanks for trying that out. This is bad news to us then as it seems to be
>an actually still existing bug.
>
>> If I config http.proxy as localhost:9050, I get error: Proxy CONNECT
>> aborted.
>> If I config http.proxy using some port forwarding tools, such as corkscrew
>> or connect, I get Send failure: Connection reset by peer.
>> I don't know the difference of these two configurations, and how to choose
>> the proper one. Why I can't use socks proxy while using git? Thanks.
>
>Isn't http.proxy saying that the proxy is a HTTP proxy, and that's why it
>sends a HTTP CONNECT request to it (that fails) ?
>
>If you start out without git in the mix, can you try using the command line
>curl tool to go over the SOCKS proxy to download data off a remote HTTPS site?
>
>--
>
> / daniel.haxx.se
>-------------------------------------------------------------------
>List admin: http://cool.haxx.se/list/listinfo/curl-library
>Etiquette: http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-08-04