git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: cURL in git for windows does not support HTTP/2 anymore

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 24, 2025, 12:52 UTC
Message-ID
<1cb70ac5-31ee-ec1b-dea5-e900f28a38f2@gmx.de>
In-Reply-To
<GV1PR10MB76004D6F2617B561A7718A099B852@GV1PR10MB7600.EURPRD10.PROD.OUTLOOK.COM>
Hi Lars,
On Thu, 24 Apr 2025, Lars Eriksen - DSV wrote:
Show 8 quoted lines
> What did you do before the bug happened? (Steps to reproduce your issue)
> Upgraded to a recent git for windows found here: https://git-scm.com/downloads
> 
> What did you expect to happen? (Expected behavior)
> The embedded curl should be able to use HTTP/2 against our backend.
> 
> What happened instead? (Actual behavior)
> After updating git for windows curl is unable to authenticate to our backend that requires HTTP/2. curl --version shows it is not compiled in. It worked in the prior version, 2.39.0.windows.2
Careful: `curl.exe` does not necessarily show the same capabilities as are
in effect when using Git. The reason is that the default SSL/TLS backend
is Secure Channel, whereas Git can be configured to use OpenSSL instead.

And looking at the most recent build of Git for Windows' cURL, I see in https://github.com/git-for-windows/git-for-windows-automation/actions/runs/14221753030/job/39851304688#step:16:1230 that the OpenSSL version is compiled with HTTP/2 support whereas https://github.com/git-for-windows/git-for-windows-automation/actions/runs/14221753030/job/39851304688#step:16:2854 shows that the Secure Channel version is compiled without HTTP/2 support.

When you configure `http.sslBackend = openssl`, does it work then?

Ciao, Johannes

P.S.: The bug reporting template of `git bugreport` sadly omits useful hints such as including the contents of `/etc/install-options.txt`, where others could easily see whether you chose the Secure Channel or the OpenSSL backend as Git's default.

Show 34 quoted lines
> 
> What's different between what you expected and what actually happened?
> I expected curl to be able to run as before when contacting our backend in our maintenance scripts. I'm not allowed to install a custom curl on our corporate network, and the windows version does not support HTTP/2 either. But the git version used to.
> 
> Anything else you want to add:
> 
> Please review the rest of the bug report below.
> You can delete any lines you don't wish to share.
> 
> 
> [System Info]
> git version:
> git version 2.49.0.windows.1
> cpu: x86_64
> built from commit: cca1f38702730b35f52c29efd62864b85e85ddcc
> sizeof-long: 4
> sizeof-size_t: 8
> shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
> feature: fsmonitor--daemon
> libcurl: 8.12.1
> OpenSSL: OpenSSL 3.2.4 11 Feb 2025
> zlib: 1.3.1
> uname: Windows 10.0 20348
> compiler info: gnuc: 14.2
> libc info: no libc information available
> $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
> 
> 
> [Enabled Hooks]
> not run from a git repository - no hooks to show
> 
> DSV internal
> 
> 
Previous: Lars Eriksen - DSVNext: Lars Eriksen - DSV
Message 2 of 5 in “cURL in git for windows does not support HTTP/2 anymore”
  1. Lars Eriksen - DSVApr 24, 2025
  2. Johannes SchindelinApr 24, 2025
  3. Lars Eriksen - DSVApr 25, 2025
  4. Johannes SchindelinApr 25, 2025
  5. Lars Eriksen - DSVApr 25, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.