Proxy Config

[Murillo Ivamoto]

I tried set up proxy on Git for Windows 2.5.0.

Fetch and pull function normally, but push never works.

What's going on??? Any idea???

[Johannes Schindelin]

Hi Murillo,

On 2015-08-20 17:01, Murillo Ivamoto wrote:
> I tried set up proxy on Git for Windows 2.5.0.
>
> Fetch and pull function normally, but push never works.

Could you be a little bit more verbose? I.e. *how* did you set up a
proxy, which proxy (is it SOCKS or HTTP? Has it worked with anything
else than Git for Windows 2.5.0 before?)? What was the exact error
message? If you try to push via SSH, does an explicit SSH call work?

Ciao,
Johannes

[Murillo Ivamoto]

Ok, Johannes. Sorry about the little information.

It's a proxy HTTPS. There is no error messages. Just try to push that there is no answer. I tried via SSH, but is also blocked.

The latest version of Msysgit the proxy configuration normally occurs.

I updated to 2.5.0 (Git for Windows) and the push does not work anymore, except for Eclipse plugins or other softwares.

[Johannes Schindelin]

Hi Murillo,

On 2015-08-21 13:25, Murillo Ivamoto wrote:

> It's a proxy HTTPS. There is no error messages. Just try to push that
> there
> is no answer. I tried via SSH, but is also blocked.

What did it say? There must be error messages, and you can ramp up the
debug level by calling `ssh -v -v -v -v <ssh-arguments>`.

Ciao,
Johannes

[Murillo Ivamoto]

I cloned my repository via HTTPS and I make operations over HTTPS as well.

For operations work properly, I set up a proxy whose address is something like "http: // user: p...@proxy.com.br: 8080". With this configuration operations should work perfectly (at least via HTTPS).

The amazing thing is that all except the push, work. In other words, make the command git push the username and password are required, and from there is not any files transmitted and not get connection error response, lock or anything else.

[Johannes Schindelin]

Hi Murillo,

On 2015-08-21 16:31, Murillo Ivamoto wrote:
> I cloned my repository via HTTPS and I make operations over HTTPS as
> well.

Okay. This is important information. I had to assume something, and I
assumed that you used SSH for pushing.

> For operations work properly, I set up a proxy whose address is
> something
> like "http: // user: p...@proxy.com.br: 8080". With this configuration
> operations should work perfectly (at least via HTTPS).

But how? Do you configure Git via `git config` or do you set the
environment variable `https_proxy`, or yet another way to configure it?

> The amazing thing is that all except the push, work. In other words,
> make
> the command git push the username and password are required, and from
> there
> is not any files transmitted and not get connection error response,
> lock or
> anything else.

You should be able to understand better what is going on by setting the
environment variable `GIT CURL_VERBOSE` before pushing.

Ciao,
Johannes

[Murillo Ivamoto]

First let https_proxy set the environment variable, which was exactly the setting that was working in msysgit 1.9.5.

How did not work, set the settings in the following ways Git itself:

1 - I configured HTTP (which is what's in the documentation): git config --global http.proxy "http: // user: p...@proxy.com.br: 8080";

2 - How well it did not work, set another configuration as suggested in various forums: git config --global https.proxy "http: // user: p...@proxy.com.br: 8080".

In all these cases it was unable to push.

I tested as suggested by you, Johannes: Setting the GIT_CURL_VERBOSE variable and try to make the push.

In response I got the following result:

< HTTP/1.0 407 Proxy Authentication Required

< Server: squid/3.1.14

< Mime-Version: 1.0

< Date: Fri, 21 Aug 2015 16:19:25 GMT

< Content-Type: text/html

< Content-Length: 1187

< X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0

< Proxy-Authenticate: NTLM

< Proxy-Authenticate: Basic realm="PROXY"

< X-Cache: MISS from proxy.com.br

< X-Cache-Lookup: NONE from proxy.com.br:8080

< Via: 1.0 proxy.com.br (squid/3.1.14)

< Connection: close

<

* Ignore 1187 bytes of response-body

* Connect me again please

* ALPN, offering http/1.1

* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH

* successfully set certificate verify locations:

*   CAfile: C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt

  CApath: none

* SSL re-using session ID

* Unknown SSL protocol error in connection to github.com:443

* Closing connection 402

* Couldn't find host github.com in the _netrc file; using defaults

* NTLM-proxy picked AND auth done set, clear picked!

* timeout on name lookup is not supported

* Hostname proxy.com.br was found in DNS cache

*   Trying 1.1.1.1...

* Connected to proxy.com.br (1.1.1.1) port 3128 (#403)

* Establish HTTP proxy tunnel to github.com:443

> CONNECT github.com:443 HTTP/1.1

Host: github.com:443

User-Agent: git/2.5.0.windows.1

Proxy-Connection: Keep-Alive

This result me was printed several times, as if estives in an infinite loop.

P.S .: URLs and addresses are fictitious.

[Johannes Schindelin]

Hi Murillo,

On 2015-08-21 18:36, Murillo Ivamoto wrote:

> * Unknown SSL protocol error in connection to github.com:443
> * Closing connection 402

This looks worrisome.

Ciao,
Johannes