Hi all, I'm trying to push to a smart HTTP remote using the following command line: http_proxy=localhost:4242 git push -v http://xxxxx:25989/git/foo +refs/heads/*:refs/heads/* (The weird proxy and port are not under my control.) The webserver should return 401 for unauthorized access, and indeed it does: error: RPC failed; result=65, HTTP code = 401 (The rest of the error text from git push is not particularly useful, but I'm not worried about that at the moment.) Making a request manually with curl --netrc shows that the auth header is being sent[1]. But sniffing the HTTP traffic from git shows that the auth header is not sent[2]. I also tried various other things like aliasing xxxxx to 127.0.0.1 and removing the proxy and port number, and specifying user@xxxxx in the URL, and nothing I've done makes git send the necessary auth header. (In the last case it does prompt for a password.) Anyone have any other ideas? I could swear this was working a few weeks ago, so I must be missing something simple. [1] $ http_proxy=localhost:4242 curl -vvn http://xxxxx:25989/git/foo/info/refs?service=git-receive-pack * About to connect() to proxy localhost port 4242 (#0) * Trying ::1... Connection refused * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 4242 (#0) * Server auth using Basic with user 'yyyyy' <---- > GET http://xxxxx:25989/git/foo/info/refs?service=git-receive-pack HTTP/1.1 > Authorization: Basic zzzzzzzz <---- > User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15 > Host: xxxxx:25989 > Accept: */* > Proxy-Connection: Keep-Alive > < HTTP/1.1 200 OK ... [2] GET http://xxxxx:25989/git/foo/info/refs?service=git-receive-pack HTTP/1.1 User-Agent: git/1.7.4.rc0 Host: xxxxx:25989 Accept: */* Proxy-Connection: Keep-Alive Pragma: no-cache -- 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