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

Re: [PATCH] Add an option for using any HTTP authentication scheme, not only basic

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 14, 2009, 21:42 UTC
Message-ID
<alpine.DEB.1.00.0904142342130.10279@pacific.mpi-cbg.de>
In-Reply-To
<Pine.LNX.4.64.0904150007130.7479@localhost.localdomain>
Hi,
On Wed, 15 Apr 2009, Martin Storsjö wrote:
Show 19 quoted lines
> On Tue, 14 Apr 2009, Johannes Schindelin wrote:
> 
> > In six months from now, it might be easier to read
> > 
> > #if LIBCURL_VERSION_NUM >= 0x070a06
> > #define LIBCURL_CAN_HANDLE_ANY_AUTH
> > #endif
> > 
> > [...]
> > 
> > #ifdef LIBCURL_CAN_HANDLE_ANY_AUTH
> > [...]
> > 
> > Don't you agree?
> 
> Yeah, absolutely.
> 
> Any comments on the naming of options and env variables? Otherwise, I'll 
> resend an updated version soon.
They sound sensible enough to me!

Thanks, Dscho

Previous: Martin Storsjö
Message 4 of 4 in “Add an option for using any HTTP authentication scheme, not only basic”
  1. Add an option for using any HTTP authentication scheme, not only basicMartin Storsjö, Apr 14, 2009
  2. Johannes SchindelinApr 14, 2009
  3. Martin StorsjöApr 14, 2009
  4. Johannes SchindelinApr 14, 2009

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.