From: Tay Ray Chuan <rctay89@gmail.com>
To: David Borowitz <dave@bwitz.com>
Cc: git@vger.kernel.org
Subject: Re: HTTP push not respecting .netrc
Date: Fri, 31 Dec 2010 12:03:24 +0800 [thread overview]
Message-ID: <AANLkTi=4cE711TtqE0E-05s9Pk72C8OymNf_-5NhrfXS@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik84-zRwi+0dGGFoTUrj6Zr3bxO=fE9P_3MuZdZ@mail.gmail.com>
On Thu, Dec 30, 2010 at 2:56 PM, David Borowitz <dave@bwitz.com> wrote:
> I'm trying to push to a smart HTTP remote using the following command line:
> http_proxy=localhost:4242 git push -v http://xxxxx:25989/git/foo
> +refs/heads/*:refs/heads/*
> (The weird proxy and port are not under my control.)
>
> The webserver should return 401 for unauthorized access, and indeed it does:
> error: RPC failed; result=65, HTTP code = 401
> (The rest of the error text from git push is not particularly useful,
> but I'm not worried about that at the moment.)
Could you run the push with the environment variable GIT_CURL_VERBOSE=1?
> [2]
> GET http://xxxxx:25989/git/foo/info/refs?service=git-receive-pack HTTP/1.1
> User-Agent: git/1.7.4.rc0
> Host: xxxxx:25989
> Accept: */*
> Proxy-Connection: Keep-Alive
> Pragma: no-cache
Try having a entry for xxxxx:25989 in your .netrc - that should be
sufficient to demonstrate to you that git+curl reads your .netrc.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-12-31 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 6:56 HTTP push not respecting .netrc David Borowitz
2010-12-31 4:03 ` Tay Ray Chuan [this message]
2011-01-13 0:42 ` Junio C Hamano
2011-01-13 0:48 ` David Borowitz
[not found] ` <AANLkTikSV5OPrtbwq-X9SknNAEHQX_gHVFc8YZu0g4+N@mail.gmail.com>
[not found] ` <AANLkTin8cxi_5_Rx6s_C2NjgGWYhUX+kdV5E1A_FYc_j@mail.gmail.com>
[not found] ` <AANLkTi=cqsvXb3eywTfxAg9hH9cigumSQjoHqq5bnJfM@mail.gmail.com>
2011-01-27 2:47 ` David Borowitz
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='AANLkTi=4cE711TtqE0E-05s9Pk72C8OymNf_-5NhrfXS@mail.gmail.com' \
--to=rctay89@gmail.com \
--cc=dave@bwitz.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.