Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

It happened when I was cloning a repo. It got stucked and throw such an error:

POST git-upload-pack (201 bytes)
error: RPC failed; curl 1 Received HTTP/0.9 when not allowed
fatal: the remote end hung up unexpectedly
I searched it online and got this:PHP Curl - Received HTTP/0.9 when not allowed Then I checked my curl version in git and I thought that it supports nghttp2
curl 7.75.0 (x86_64-w64-mingw32) libcurl/7.75.0 OpenSSL/1.1.1k (Schannel) zlib/1.2.11 brotli/1.0.9 zstd/1.4.8 libidn2/2.3.0 libssh2/1.9.0 nghttp2/1.41.0
Release-Date: 2021-02-03
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz Metalink MultiSSL NTLM SPNEGO SSL SSPI TLS-SRP zstd
I also tried other solutions such as setting http.postBuffer (from https://medium.com/swlh/everything-you-need-to-know-to-resolve-the-git-push-rpc-error-1a865fd1ebea) but they didn't work. I'm pretty confused.. Does anyone have any idea
By the way, I am not an English native speaker. please forgive me if there's any error about grammar.
                The http.postBuffer option has no effect on clones, and the Git FAQ outlines why you should not use it without understanding what it does.  The problem here is either the remote server or something on your system (e.g., firewall, antivirus, proxy, MITM device) that is intercepting your connection.
– bk2204
                Apr 12, 2021 at 22:28
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.