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

Re: git https transport and wrong password

From
Mikko Rapeli <mikko.rapeli@iki.fi>
Date
Apr 3, 2013, 09:43 UTC
Message-ID
<20130403094302.GY30514@lakka.kapsi.fi>
In-Reply-To
<20130402202054.GX30514@lakka.kapsi.fi>

Maybe my git installation was incomplete before when running from ~/bin since I was not able to set break points to http_request() and some debug code was not there until I ran git through bin-wrappers in the source tree.

I added some debug prints to http.c functions http_request() and handle_curl_result(), and now I see this chain of events:

 http_request_reauth()
 http_request()
 GET ...info/refs?service=git-upload-pack
 HTTP/1.1 401 Authorization Required
* Ignoring the response-body
* Issue another request to this URL: '...'
 GET ...info/refs?service=git-upload-pack
 HTTP/1.1 401 Authorization Required
 handle_curl_result: res = 22, http_code = 401, user = ..., pass = (null)
Password for '...': (enter valid password)
 GET ...info/refs?service=git-upload-pack
 HTTP/1.1 200 OK

So, for some reason the first GET request is issued twice and first 401 is ignored. I'll try to debug run_active_slot() next...

-Mikko
Previous: Mikko RapeliNext: Jeff King
Message 7 of 9 in “git https transport and wrong password”
  1. Mikko RapeliApr 2, 2013
  2. Mikko RapeliApr 2, 2013
  3. Jeff KingApr 2, 2013
  4. Mikko RapeliApr 2, 2013
  5. Jeff KingApr 2, 2013
  6. Mikko RapeliApr 2, 2013
  7. Mikko RapeliApr 3, 2013
  8. Jeff KingApr 3, 2013
  9. Mikko RapeliApr 3, 2013

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.