git 2.20.1.windows.1 does not honor http.sslverify=false

Question

After the latest update (in fact, I did a new install) of git for Windows I cannot connect to a specific remote repository any longer via https. It\'s on an in-house server

Answer 1

Try first and access your repo in a CMD session where you set a simplified PATH, using a portable Git for Windows (PortableGit-2.20.1-64-bit.7z.exe), uncompressed in C:\Git:

set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\
set GH=C:\path\to\git
set PATH=%GH%\bin;%GH%\usr\bin;%GH%\mingw64\bin;%PATH%

Then try to access your repo in that session.

---

Edit by the OP, Peter: The test with an uncluttered environment worked. The difference is with the environment variables https_proxy and HTTPS_PROXY which both must be unset.¹ This is true even though the server is listed in the no_proxy environment variable which normally instructs programs to not use a proxy for specific servers listed in the variable value. Luckily the repo server is in the local network.²

It's unclear to me whether git proper, cURL or openssl is the culprit here; the variables are, I believe, evaluated by git proper as well as the networking libraries.

---

¹I think it's for historical reasons that the variable exists in an upper-case and lower-case form.

² As far as I can tell the issue is not with the proxy server because the repo server certificate is obtained and correctly recognized as self-certified.