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

Re: Git clone sends first an empty authorization header

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Mar 5, 2016, 08:47 UTC
Message-ID
<m2r3fpgvk7.fsf@linux-m68k.org>
In-Reply-To
<CAMDzUty+O2Gu7o4bFib71AaNZn647WQ1v7ceiznHOs7-xwZGUg@mail.gmail.com>
Guilherme <guibufolo@gmail.com> writes:
Show 5 quoted lines
> When doing basic authentication using git clone by passing the
> username and password in the url git clone will first send a GET
> request without the authorization header set.
>
> Am i seeing this right?

Yes, that is the correct way to implement HTTP authentication. The client won't know which authentication method to use until the server tells it.

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: Guilherme
Message 4 of 4 in “Git clone sends first an empty authorization header”
  1. GuilhermeMar 5, 2016
  2. Bryan TurnerMar 5, 2016
  3. GuilhermeMar 5, 2016
  4. Andreas SchwabMar 5, 2016

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.