On 29 Jan 2013, at 15:11, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 29 Jan 2013, at 14:49, Damien Cassou <damien.cassou@gmail.com> wrote:
On Tue, Jan 29, 2013 at 1:46 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
You are correct: username/password in URLs is not something that is supported by ZnUrl, by design actually.
Why do you need it ?
we are implementing the Git protocol with the HTTP backend. Git urls often comes with username inside and that's why we thought it would be easier to just use #asZnUrl. And these username and password elements are part of the standard (http://en.wikipedia.org/wiki/URI_scheme#Examples).
I will see if I can add it in an elegant way.
I still feel it is a bit old school, from the FTP days, 99% of URLs won't ever have this.
But yes, I know it is used in some places, like git...
I added this (in bleedingEdge) so that 'git://user@foo.com/bar' asZnUrl works as expected. Sven ==================== Summary ==================== Name: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.9 Author: SvenVanCaekenberghe Time: 30 January 2013, 7:41:44 am UUID: 9c2126e3-8881-49f5-8d59-38efbb6d796d Ancestors: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.8 Extended ZnUrl to support the optional user info (username and optional password) component; Modified ZnUrl to allow any scheme, added #enforceKnownScheme -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill