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

Re: Why does fetch-pack not works over http?

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Oct 27, 2017, 12:33 UTC
Message-ID
<873764bwjd.fsf@linux-m68k.org>
In-Reply-To
<1509100979.32292.19.camel@bitergia.com>
On Okt 27 2017, Alvaro del Castillo <acs@bitergia.com> wrote:
Show 18 quoted lines
> We're wondering why "fetch-pack" (when is running from the command
> line) doesn't handle "https://" protocol. It only works with "git://".
>
> For instance, this doesn't work:
>
> $ git fetch-pack https://github.com/git/git refs/heads/master
> fatal: I don't handle protocol 'https'
>
> while this does:
>
> $ git fetch-pack git://github.com/git/git refs/heads/master
>
> The funny thing is that under the hood, "fetch" calls "fetch-pack"
> using "https" procotol. Example of a trace below:
>
> 12:03:07.512558 git.c:344               trace: built-in: git 'fetch-
> pack' '--stateless-rpc' '--stdin' '--lock-pack' '--thin' 'https://githu
> b.com/git/git/'

With --stateless-rpc, fetch-pack doesn't do the connect itself, but expects the caller having set up a pipe to it. The URL is then actually ignored.

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Alvaro del CastilloNext: Alvaro del Castillo
Message 2 of 3 in “Why does fetch-pack not works over http?”
  1. Alvaro del CastilloOct 27, 2017
  2. Andreas SchwabOct 27, 2017
  3. Alvaro del CastilloOct 30, 2017

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.