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

Re: HTTP push not respecting .netrc

From
DBDavid Borowitz <dave@bwitz.com>
Date
Jan 27, 2011, 02:47 UTC
Message-ID
<AANLkTi=k5m+90wZPLMjah3cnL=4PjF5Skp2zkaTXyD09@mail.gmail.com>
In-Reply-To
<AANLkTi=cqsvXb3eywTfxAg9hH9cigumSQjoHqq5bnJfM@mail.gmail.com>
On Wed, Jan 26, 2011 at 18:00, David Borowitz <dave@bwitz.com> wrote:
> But this raises further questions:
> -Why does git/curl decide it's ok to retry with authentication in one
> case, but not in the other?

Poking further, it looks like curl is deciding not to retry because the ioctl callback is failing to rewind the post buffer when clearly it should be able to. So it's more likely a git bug than a curl issue (the following question notwithstanding).

> -Why does curl send the auth header before ever receiving a 401, while
> git does not? (Would fixing this be as easy as setting another curl
> option?)
Previous: David Borowitz
Message 5 of 5 in “HTTP push not respecting .netrc”
  1. David BorowitzDec 30, 2010
  2. Tay Ray ChuanDec 31, 2010
  3. Junio C HamanoJan 13, 2011
  4. David BorowitzJan 13, 2011
  5. David BorowitzJan 27, 2011

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.