Home / server / Questions / 409616
Accepted
Jayen
Asked: 2012-07-21 05:12:49 +0800 CST

git refuses to send credentials over HTTP

  • 772

curl seems to work fine, but git does not. git asks for a password, but then doesn't send any credentials.

Works: curl --netrc http://test.git.unsw.edu.au/ and curl -u username:password http://test.git.unsw.edu.au/

Doesn't work: git remote update

Password for 'http://[email protected]': 
* Couldn't find host test.git.unsw.edu.au in the .netrc file; using defaults
User-Agent: git/1.7.9.5
Host: test.git.unsw.edu.au
Accept: */*
Pragma: no-cache

Why isn't git sending credentials?

From an strace, I see:

  1. Read .netrc
  2. GET /repo/info/refs?service=git-receive-pack HTTP/1.1 - no credentials
  3. HTTP/1.0 401 Unauthorized
  4. Read .netrc
  5. GET /repo/info/refs?service=git-receive-pack HTTP/1.0 - no credentials
  6. HTTP/1.0 401 Unauthorized
  7. Prompt for password
  8. Read .netrc
  9. * Couldn't find host test.git.unsw.edu.au in the .netrc file; using defaults
  10. GET /repo/info/refs?service=git-receive-pack HTTP/1.1 - no credentials
  11. HTTP/1.0 401 Unauthorized
authentication

2 Answers

  1. Best Answer

    Git seems to only use CURLAUTH_ANY which does not work with my particular web server. My web server supports Negotiate and Basic, so Git does not fallback to Basic when Negotiate is not available on the client.

    Further, there seems to be no option to Git to use anything other than CURLAUTH_ANY.

    • 1

  2. Looking at the manpage, it seems git doesn't take the username option when used with http. But if you put it in your .netrc file, curl should use it. The format for .netrc is

    machine hostname login yourusername password yourpassword
    • 0