From: "Peter Odéus" <peter.odeus@gmail.com>
To: git@vger.kernel.org
Subject: From 200 to 404 to 407.
Date: Tue, 27 Oct 2009 11:18:44 +0100 [thread overview]
Message-ID: <82fd2c5d0910270318wc30bc44tfd3362933d3f62cf@mail.gmail.com> (raw)
Hi,
Doing a "git clone..." using authenticated proxy (set in $http_proxy):
Upon initial success (HTTP 200) and receiving a single HTTP 404 (not
found), every GET after that renders a HTTP 407 (Proxy authentication
required).
curl -I "url_giving_http_407" comes out just fine as a HTTP 200.
Bug or just me?
next reply other threads:[~2009-10-27 10:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 10:18 Peter Odéus [this message]
2009-10-27 16:53 ` From 200 to 404 to 407 Avery Pennarun
2009-10-28 15:02 ` Peter
2009-10-28 15:35 ` Peter Odéus
[not found] ` <82fd2c5d0910280138r52baff98p3f4ff65e968b0d37@mail.gmail.com>
2009-10-28 15:50 ` Avery Pennarun
2009-10-28 16:10 ` Peter Odéus
2009-10-28 16:35 ` Avery Pennarun
2009-10-28 16:48 ` Avery Pennarun
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=82fd2c5d0910270318wc30bc44tfd3362933d3f62cf@mail.gmail.com \
--to=peter.odeus@gmail.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 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).