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

Re: [PATCH] http.proxy: also mention https_proxy and all_proxy

From
Clemens Buchacher <drizzd@aon.at>
Date
Mar 4, 2012, 12:46 UTC
Message-ID
<20120304124627.GA1596@ecki>
In-Reply-To
<7v399p72a8.fsf@alter.siamese.dyndns.org>
On Sat, Mar 03, 2012 at 02:22:39PM -0800, Junio C Hamano wrote:
> 
> As to the way forward, I suspect that http.proxy was a mistake to begin
> with, considering the structure of namespace our configuration variables
> fit in.  Shouldn't they be proxy.http, proxy.https, etc.?

I actually prefer the current behavior, which is to configure only one proxy for all protocols. I have not seen a setup where HTTP and HTTPS are routed through different proxies before. But if this is really needed, one has the option to use the environment variable, or remote.<name>.proxy.

I suggest instead that we map curl's CURLOPT_PROXY to core.proxy. That would also fit well with the remote.<name>.proxy scheme.

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 8 in “http.proxy: also mention https_proxy and all_proxy”
  1. http.proxy: also mention https_proxy and all_proxyClemens Buchacher, Mar 3, 2012
  2. Jeff KingMar 3, 2012
  3. [RFH] 'man:' macro for asciidocJakub Narebski, Mar 3, 2012
  4. Junio C HamanoMar 3, 2012
  5. Clemens BuchacherMar 4, 2012
  6. Junio C HamanoMar 4, 2012
  7. http.proxy: also mention https_proxy and all_proxyClemens Buchacher, Mar 4, 2012
  8. Junio C HamanoMar 5, 2012

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.