sftp bugs

[Jan Hudec]

On Tue, Nov 29, 2005 at 20:12:35 -0600, John Arbash Meinel wrote:
> I was waiting to pull in the sftp changes because of the change to path
> specifications. Are we settled that we want to accept:
> 
> sftp://user:pass@host/relative/path
> and
> sftp://user:pass@host//root/path
> 
> Personally, I don't see why we don't make it more like the sftp program
> itself, we certainly could do:
> 
> sftp://user:pass@host:/root/path
> sftp://user:pass@host:relative/path
> 
> I prefer the latter, but I guess the former is some sort of Draft spec.

Unfortunately the later does not really work, because you can also have:
sftp://user:pass@host:443/path
and even this should probably work (using /etc/services):
sftp://user:pass@host:https/path
And that obviously colides. Sftp solves that by using option or config
entry for that, but bzr should encode in the URL.

Also mercurial already settled on the double slash for relative (the
draft actually says the second slash must be URI-encoded as %2F, but
accepting it unencoded (too) should not harm anyone), so there is some
precedent now.

--
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051130/a1f101d0/attachment.pgp