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 25, 2025, 11:44 UTC
Message-ID
<01fd2b48-dc9e-ec69-b4f9-1183beb7f8a8@gmx.de>
In-Reply-To
<GV1PR10MB76004ED8EC327A2D11EDD2CB9B842@GV1PR10MB7600.EURPRD10.PROD.OUTLOOK.COM>
Hi Lars,
On Fri, 25 Apr 2025, Lars Eriksen - DSV wrote:
Show 6 quoted lines
> I'm sorry for the confusion, but the problem is not within the git
> command itself. This works fine. But we use the distributed curl command
> for POSTing data in a custom script when we deploy to production.
>
> So the problem is with how the curl command is built for windows. It
> used to be built with HTTP/2 support, now it is not.

I am sorry, but Git for Windows is not really intended as a distribution model for the `curl.exe` command, it merely is shipped in Git for Windows because some scripts require it.

Have you tried using the `curl.exe` in `C:\Windows\system32`? If that does not work, you may need to switch to MSYS2 (which is a proper software distribution, not a hard-baked one like Git for Windows that includes bits and pieces necessary to run Git commands).

Ciao, Johannes

Previous: Lars Eriksen - DSVNext: Lars Eriksen - DSV
Message 4 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.