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

FYI: git issues with libcurl 8.0/1 HTTPS push

From
Daniel Stenberg <daniel@haxx.se>
Date
Aug 22, 2023, 11:32 UTC
Message-ID
<qq3252n1-o71-n1r7-281p-npqo6rs5o50@unkk.fr>
Hello friends.

If you use git with libcurl 8.0.x or 8.1.x, there is a risk that you will experience a "curl 56 HTTP/2 stream N was reset" errors when pushing over HTTPS. (where N is an odd number, often 7)

This is an unfortunate bug in libcurl that has subsequently already been fixed. We recommend using libcurl 8.2.1 (or later).

You can work around this issue (that tends to be sticky) by forcing git to use HTTP/1.1 instead of HTTP/2 for the push and then restore back to the previous state again.

This bug was filed and has been discussed in this curl issue:
   https://github.com/curl/curl/issues/11353
I'm sorry for this incovenience.
-- 
  / daniel.haxx.se
Next: Junio C Hamano
Message 1 of 4 in “FYI: git issues with libcurl 8.0/1 HTTPS push”
  1. Daniel StenbergAug 22, 2023
  2. Junio C HamanoAug 22, 2023
  3. Daniel StenbergAug 22, 2023
  4. Junio C HamanoAug 22, 2023

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.