From: Ben Humphreys <behumphreys@atlassian.com>
To: git@vger.kernel.org
Subject: Git 2.23.0-rc0 HTTP authentication failure - error message change
Date: Tue, 18 May 2021 13:07:36 +1000 [thread overview]
Message-ID: <YKMvePOPqjwiXeQ+@C02WD045HTDG> (raw)
Hi,
I've run 2.32.0-rc0 through the Bitbucket Server test matrix and it picked up a
change in error message that perhaps is unintentional.
On 2.31.1:
$ git ls-remote http://notauser@localhost:7990/bitbucket/scm/project_1/rep_1.git
Password for 'http://notauser@localhost:7990':
fatal: Authentication failed for 'http://localhost:7990/bitbucket/scm/project_1/rep_1.git/'
and on 2.32.0-rc0:
$ git ls-remote http://notauser@localhost:7990/bitbucket/scm/project_1/rep_1.git
Password for 'http://notauser@localhost:7990':
fatal: unable to access 'http://localhost:7990/bitbucket/scm/project_1/rep_1.git/': The requested URL returned error: 401
This appears to be a side effect of 1b0d9545bb8, if I revert that commit the old
behavior returns. Certainly we can update our pattern matching to match the new message,
but I wonder if the old message is preferred for folks who are not familiar with HTTP
status codes.
Best Regards,
Ben Humphreys
next reply other threads:[~2021-05-18 3:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 3:07 Ben Humphreys [this message]
2021-05-18 5:50 ` Git 2.23.0-rc0 HTTP authentication failure - error message change Jeff King
2021-05-18 6:26 ` [PATCH 0/2] fix v2.32.0-rc0 bug with Negotiate / HTTP_NOAUTH Jeff King
2021-05-18 6:27 ` [PATCH 1/2] t5551: test http interaction with credential helpers Jeff King
2021-05-18 6:27 ` [PATCH 2/2] Revert "remote-curl: fall back to basic auth if Negotiate fails" Jeff King
2021-05-19 13:58 ` Derrick Stolee
2021-05-19 14:14 ` Jeff King
2021-05-19 14:53 ` Derrick Stolee
2021-05-19 1:12 ` [PATCH 0/2] fix v2.32.0-rc0 bug with Negotiate / HTTP_NOAUTH Junio C Hamano
2021-05-19 0:12 ` Git 2.23.0-rc0 HTTP authentication failure - error message change brian m. carlson
2021-05-19 11:49 ` 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=YKMvePOPqjwiXeQ+@C02WD045HTDG \
--to=behumphreys@atlassian.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.