Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. 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 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
