{"thread":{"id":"37587","subject":"Broken handling of URL with literal IPv6 address","startedAt":"2014-09-18T11:29:11Z","lastAt":"2014-09-18T13:03:32Z","messageCount":2,"participants":["Christian Taube","Torsten Bögershausen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"249632","messageId":"2004412952.561305.1411039751559.open-xchange@app02.ox.hosteurope.de","threadId":"37587","inReplyTo":null,"subject":"Broken handling of URL with literal IPv6 address","fromName":"Christian Taube","fromEmail":"lists@hcf.yourweb.de","sentAt":"2014-09-18T11:29:11Z","receivedAt":"2014-09-18T11:29:11Z","isPatch":false,"sender":{"key":"lists@hcf.yourweb.de","avatar":null},"body":"\nHello,\n\nI was sent here from the IRC channel.\n\n\nUsing git 2.1.0, the command\n\n  git clone ssh://[2001:db8::1]/repo.git\n\nsucceeds, but adding a username to the URL like this\n\n  git clone ssh://user@[2001:db8::1]/repo.git\n\nfails with an invalid hostname message:\n\nCloning into 'repo.git'...\nssh: Could not resolve hostname [2001: Name or service not known\nfatal: Could not read from remote repository.\n\n\nI found this workaround:\n\n  git clone ssh://[user@2001:db8::1]/repo.git\n\nbut this seems to be contrary to the definition of URLs in RFC 3986.\n\nhttp://tools.ietf.org/html/rfc3986\n\n\nPlease have a look at this. Thank you!\n\n\n--\nChristian Taube\n"},{"id":"249633","messageId":"541AD824.2040401@web.de","threadId":"37587","inReplyTo":"2004412952.561305.1411039751559.open-xchange@app02.ox.hosteurope.de","subject":"Re: Broken handling of URL with literal IPv6 address","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2014-09-18T13:03:32Z","receivedAt":"2014-09-18T13:03:32Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On 2014-09-18 13.29, Christian Taube wrote:\n> \n> Hello,\n> \n> I was sent here from the IRC channel.\n> \n> \n> Using git 2.1.0, the command\n> \n>   git clone ssh://[2001:db8::1]/repo.git\n> \n> succeeds, but adding a username to the URL like this\n> \n>   git clone ssh://user@[2001:db8::1]/repo.git\n> \n> fails with an invalid hostname message:\n> \n> Cloning into 'repo.git'...\n> ssh: Could not resolve hostname [2001: Name or service not known\n> fatal: Could not read from remote repository.\n> \n> \n> I found this workaround:\n> \n>   git clone ssh://[user@2001:db8::1]/repo.git\n> \n> but this seems to be contrary to the definition of URLs in RFC 3986.\n> \n> http://tools.ietf.org/html/rfc3986\n> \n> \n> Please have a look at this. Thank you!\n> \n> \n> --\n> Christian Taube\n\nThis is indeed a bug.\nWe handle literal IPv6 adresses OK, we handle ssh://user@host OK.\nBut it seems as if you are the first one using the combination of both,\nthanks for the bug report.\n\nIf somebody want to have a look in the Git source tree:\nconnect.c, t/t5500-fetch-pack.sh and t/t5601-clone.sh may deserve an update.\n \n"}]}