git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/1] http: allow authenticating proactively

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 28, 2024, 22:18 UTC
Message-ID
<xmqqh6dc1zk2.fsf@gitster.g>
In-Reply-To
<Zn8yhdN6henrIqgD@tapette.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
Show 12 quoted lines
>> > +* `basic` - Request Basic authentication from the helper.
>> > +* `auto` - Don't request any scheme from the helper.
>> > +--
>> 
>> What does "don't request" exactly mean?  It is not like we are
>> telling the helper "Don't give us anything", right?  Are we telling
>> the helper "Give us any username/password for the URL in any
>> authentication scheme you know about?"
>
> It means we don't send a `wwwauth[]` entry in the request.  We are
> giving the helper carte blanche to decide what scheme is best (maybe it
> knows we want Bearer, for example).

Well, at least I couldn't read the proposed document update and read that much out of it, and I suspect there may be other readers who will share my confusion. I think the source of the confusion is that "don't request" does not automatically imply "allow the helper to pick any scheme as it sees fit" if you do not know how helper is designed to behave when it is not requested "any scheme".

    `basic` - Request Basic authentication from the helper.
    `auto`  - Ask the helper to pick an appropriate scheme.
    `none`  - Disable proactive authentication.
or something, perhaps?
Thanks.
Previous: brian m. carlsonNext: brian m. carlson
Message 5 of 12 in “Proactive authentication over HTTP”
  1. 0/1 Proactive authentication over HTTPbrian m. carlson, Jun 28, 2024
  2. 1/1 http: allow authenticating proactivelybrian m. carlson, Jun 28, 2024
  3. Junio C HamanoJun 28, 2024
  4. brian m. carlsonJun 28, 2024
  5. Junio C HamanoJun 28, 2024
  6. brian m. carlsonJun 29, 2024
  7. Junio C HamanoJul 1, 2024
  8. 0/1 Proactive authentication over HTTPbrian m. carlson, Jul 4, 2024
  9. 1/1 http: allow authenticating proactivelybrian m. carlson, Jul 4, 2024
  10. Junio C HamanoJul 4, 2024
  11. 0/1 Proactive authentication over HTTPbrian m. carlson, Jul 10, 2024
  12. 1/1 http: allow authenticating proactivelybrian m. carlson, Jul 10, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.