On Sat, Dec 10, 2011 at 09:56:07AM +0100, Mathieu Peltier wrote: [...] > 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html