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

Re: From 200 to 404 to 407.

From
Avery Pennarun <apenwarr@gmail.com>
Date
Oct 28, 2009, 16:48 UTC
Message-ID
<32541b130910280948u57535c2bnbc30424b7ef13e2a@mail.gmail.com>
In-Reply-To
<loom.20091028T170227-957@post.gmane.org>
On Wed, Oct 28, 2009 at 12:10 PM, Peter Odéus <peter.odeus@gmail.com> wrote:
> Anyway. Behind these corporate walls, the proxy is a reality to deal with, so
> hopefully someone else can bring us closer to a solutiuon.

I was just looking at the source and it seems all the curl-related stuff is isolated in git/http.c, and is pretty easy to understand. Since I have no way to reproduce your problem, I won't attempt to look into it myself. But if you look for "proxy" (and especially CURLOPT_PROXY) in that file, you might find something.

Specifically, I would suggest resetting the CURLOPT_PROXY setting before each URL request (eg. in new_http_object_request).

Hope this helps.
Avery
Previous: Avery Pennarun
Message 8 of 8 in “From 200 to 404 to 407.”
  1. Peter OdéusOct 27, 2009
  2. Avery PennarunOct 27, 2009
  3. PeterOct 28, 2009
  4. Peter OdéusOct 28, 2009
  5. Avery PennarunOct 28, 2009
  6. Peter OdéusOct 28, 2009
  7. Avery PennarunOct 28, 2009
  8. Avery PennarunOct 28, 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.