From: "Torsten Bögershausen" <tboegi@web.de>
To: Christian Taube <lists@hcf.yourweb.de>, git@vger.kernel.org
Subject: Re: Broken handling of URL with literal IPv6 address
Date: Thu, 18 Sep 2014 15:03:32 +0200 [thread overview]
Message-ID: <541AD824.2040401@web.de> (raw)
In-Reply-To: <2004412952.561305.1411039751559.open-xchange@app02.ox.hosteurope.de>
On 2014-09-18 13.29, Christian Taube wrote:
>
> Hello,
>
> I was sent here from the IRC channel.
>
>
> Using git 2.1.0, the command
>
> git clone ssh://[2001:db8::1]/repo.git
>
> succeeds, but adding a username to the URL like this
>
> git clone ssh://user@[2001:db8::1]/repo.git
>
> fails with an invalid hostname message:
>
> Cloning into 'repo.git'...
> ssh: Could not resolve hostname [2001: Name or service not known
> fatal: Could not read from remote repository.
>
>
> I found this workaround:
>
> git clone ssh://[user@2001:db8::1]/repo.git
>
> but this seems to be contrary to the definition of URLs in RFC 3986.
>
> http://tools.ietf.org/html/rfc3986
>
>
> Please have a look at this. Thank you!
>
>
> --
> Christian Taube
This is indeed a bug.
We handle literal IPv6 adresses OK, we handle ssh://user@host OK.
But it seems as if you are the first one using the combination of both,
thanks for the bug report.
If somebody want to have a look in the Git source tree:
connect.c, t/t5500-fetch-pack.sh and t/t5601-clone.sh may deserve an update.
prev parent reply other threads:[~2014-09-18 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 11:29 Broken handling of URL with literal IPv6 address Christian Taube
2014-09-18 13:03 ` Torsten Bögershausen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541AD824.2040401@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=lists@hcf.yourweb.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).