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

Re: Access to git repository through squid proxy: The remote end hung up unexpectedly

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Dec 10, 2011, 22:58 UTC
Message-ID
<20111210225818.GM2525@localhost.localdomain>
In-Reply-To
<CACjeFCA4h_w2UmYywMBV_P+YZcWAE=zRUz-z5eTfAO+oxWKPjw@mail.gmail.com>
On Sat, Dec 10, 2011 at 09:56:07AM +0100, Mathieu Peltier wrote:
[...]
Show 14 quoted lines
> 2011/12/09 12:22:44 socat[21428] I setting option "proxyport" to "8080"
> 2011/12/09 12:22:44 socat[21428] I setting option
> "proxy-authorization" to "user:pass"
> ...
> 2011/12/09 12:22:44 socat[21428] I sending "CONNECT
> git.server.org:9418 HTTP/1.0\r\n"
> ...
> 2011/12/09 12:22:44 socat[21428] I proxy_connect: received answer
> "HTTP/1.1 403 OK\r\n"
> 2011/12/09 12:22:44 socat[21428] E CONNECT git.server.org:9418: OK
> 2011/12/09 12:22:44 socat[21428] N exit(1)
> 2011/12/09 12:22:44 socat[21428] I shutdown(3, 2)
> 2011/12/09 12:22:44 socat[21428] D shutdown()  -> 0
> fatal: The remote end hung up unexpectedly
[...]

HTTP 403 means "access denied" or "forbidden". IIRC, a proxy (or any other HTTP-speaking server) should respond with the 401 code when a client first requests a protected resource, and the client is then supposed to retry its request but this time it should provide an authentication info (and the auth mech selected). You have an ellipsis in your debug output in the place that exchange is supposed to be happening so I'm unable to dig deeper.

Looks like either your socat supplies incorrect credentials or proxy does not ask socat to actually authenticate and just denies the request.

Previous: Mathieu PeltierNext: Mathieu Peltier
Message 4 of 5 in “Access to git repository through squid proxy: The remote end hung up unexpectedly”
  1. Mathieu PeltierDec 10, 2011
  2. Konstantin KhomoutovDec 10, 2011
  3. Mathieu PeltierDec 10, 2011
  4. Konstantin KhomoutovDec 10, 2011
  5. Mathieu PeltierDec 12, 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.