Closed
Description
Setup
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
$ git --version --build-options
git version 2.39.0.windows.1
cpu: x86_64
built from commit: de9501c66f93785f7eaf10d02ef08d231eb11688
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver
Microsoft Windows [Version 10.0.18363.2274]
- What options did you set as part of the installation? Or did you choose the
defaults?
No options, just default
- Any other interesting things about your environment that might be related
to the issue you're seeing?
Git installed through Scoop package manager
Details
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
Git Bash and Powershell
- What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
PS C:\Users\MyAccount> **$env:no_proxy**
localhost,.[company-domain].ch
PS C:\Users\MyAccount> git clone https://gitlab.[company-domain].ch/...[reponame] .\scoop\buckets\[reponame]
Cloning into '.\scoop\buckets\[reponame]'...
fatal: unable to access 'https://gitlab.[company-domain].ch/.../[reponame]/': **Received HTTP code 504 from proxy after CONNECT**
- What did you expect to occur after running these commands?
That the repository is cloned
- What actually happened instead?
An error because curl tries to reach the internal repository through the proxy. It actually ignores the no_proxy environment variable
This seems to be broken in curl and already fixed. See also curl/curl#9884
It would be nice to have a Git for Windows Release that uses an older version of curl where the no_proxy variable is used correctly.
Metadata
Metadata
Assignees
Labels
No labels