From: Jeff King <peff@peff.net>
To: 王小建 <littlejian8@gmail.com>
Cc: Daniel Stenberg <daniel@haxx.se>,
git@vger.kernel.org, lj167647@alibaba-inc.com
Subject: Re: git clone with basic auth in url directly returns authentication failure after 401 received under some git versions
Date: Mon, 22 Aug 2022 05:07:33 -0400 [thread overview]
Message-ID: <YwNHVfvb10VD2ROe@coredump.intra.peff.net> (raw)
In-Reply-To: <CADmGLV0F==7ep-xZKd2crZLi8JnFBFVkdX9Bi2T63NECcSAbVw@mail.gmail.com>
On Mon, Aug 22, 2022 at 11:35:10AM +0800, 王小建 wrote:
> Thank you very much for your answer！
> And now I tried to add CURLOPT_UNRESTRICTED_AUTH but it failed.
> Here are a few examples of what I've tried.
> 1. docker run -it -e CURLOPT_UNRESTRICTED_AUTH=1 5de1a96efc49 clone
> http://xxx:xxx@xxx/xxx/xxx
> 2. echo CURLOPT_UNRESTRICTED_AUTH=1 > $HOME/.curlrc
> I wonder if it's the way I'm trying to do it wrong
That won't work. CURLOPT_UNRESTRICTED_AUTH isn't an environment
variable, but rather a flag that Git could pass to libcurl via
curl_easy_setopt(). So we'd probably wire it up in Git to a config
option. I'd prefer not to unless there is a compelling reason, though.
The documentation would have to come with a big warning/disclaimer,
which is a good sign that we may be better off without the option
entirely. :)
-Peff
next prev parent reply other threads:[~2022-08-22 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 2:51 git clone with basic auth in url directly returns authentication failure after 401 received under some git versions 王小建
2022-08-20 8:44 ` Jeff King
2022-08-20 11:59 ` 王小建
2022-08-20 22:32 ` Daniel Stenberg
2022-08-22 3:35 ` 王小建
2022-08-22 9:07 ` Jeff King [this message]
2022-08-22 9:04 ` Jeff King
2022-08-22 22:11 ` brian m. carlson
2022-08-23 20:16 ` Jeff King
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=YwNHVfvb10VD2ROe@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=daniel@haxx.se \
--cc=git@vger.kernel.org \
--cc=littlejian8@gmail.com \
--cc=lj167647@alibaba-inc.com \
/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).