From: Paul Vincent Craven <paul@cravenfamily.com>
To: "Martin Storsjö" <martin@martin.st>
Cc: git@vger.kernel.org
Subject: Re: git over http not re-authenticating after 301 redirect?
Date: Tue, 7 Apr 2009 14:25:53 -0500 [thread overview]
Message-ID: <5591393c0904071225w7d5a426ap50cb5f973e34f802@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904071041200.5901@localhost.localdomain>
On Tue, Apr 7, 2009 at 2:42 AM, Martin Storsjö <martin@martin.st> wrote:
> It's a long shot, but try see if you can upgrade to a newer version of
> libcurl; I think I saw some issue like this when I was experimenting with
> different http auth setups last week, that was solved by using newer
> versions...
No luck, but thanks for the suggestion. Updating to the March 3 build
of curl 7.19.4 yielded the same results.
--
Paul Vincent Craven
http://www.cravenfamily.com
next prev parent reply other threads:[~2009-04-07 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:14 git over http not re-authenticating after 301 redirect? Paul Vincent Craven
2009-04-07 7:42 ` Martin Storsjö
2009-04-07 19:25 ` Paul Vincent Craven [this message]
2009-04-09 17:20 ` Tay Ray Chuan
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=5591393c0904071225w7d5a426ap50cb5f973e34f802@mail.gmail.com \
--to=paul@cravenfamily.com \
--cc=git@vger.kernel.org \
--cc=martin@martin.st \
/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).