On Sat, Aug 31, 2013 at 08:52:06AM +0200, Patrick Atoon wrote:

> Here is what happens. First try cloning without specifying the user name:
> ---8<-------------------------------------------------------
> $ git clone https://git.server.com/git/test.git
> Initialized empty Git repository in /tmp/git/test/.git/
> error: The requested URL returned error: 401 Authorization Required
> while accessing
> https://git.server.com/git/test.git/nfo/refs
> fatal: HTTP request failed

That should be prompting you. What version of git are you using?

> I couldn't find a "--username" flag or something similar for the git
> command, so my next try was to incorporate the user name in the URL,
> basic auth style.

Yes, that's the correct way to do it from the command line.

If you are running v1.7.9 and later, you can also put this in your

  [credential "https://git.server.com";]
    username = user.em...@emaildomain.com

to automatically use that username for the particular domain.

> https://user.em...@emaildomain.com@git.server.com/git/test.git
> Note the double "@" there, it is bound to cause trouble.

Yes. You probably want to escape it like:


In theory we could parse from the right-hand side of the hostname and
realize that only the right-most "@" is the username separator (under
the assumption that hostnames can never contain an "@"). I don't know if
that would violate the standard or not. However, it is not even git that
does the actual parsing in this case, but rather libcurl.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to