From: Mikko Rapeli <mikko.rapeli@iki.fi>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>
Subject: Re: git https transport and wrong password
Date: Wed, 3 Apr 2013 12:43:02 +0300 [thread overview]
Message-ID: <20130403094302.GY30514@lakka.kapsi.fi> (raw)
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
next prev parent reply other threads:[~2013-04-03 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 15:54 git https transport and wrong password Mikko Rapeli
2013-04-02 16:23 ` Mikko Rapeli
2013-04-02 19:28 ` Jeff King
2013-04-02 19:47 ` Mikko Rapeli
2013-04-02 20:05 ` Jeff King
2013-04-02 20:20 ` Mikko Rapeli
2013-04-03 9:43 ` Mikko Rapeli [this message]
2013-04-03 14:12 ` Jeff King
2013-04-03 16:15 ` Mikko Rapeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130403094302.GY30514@lakka.kapsi.fi \
--to=mikko.rapeli@iki.fi \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).