On Mon, Apr 09, 2012 at 03:24:30PM -0700, Julian Elischer wrote:
> could you not parse the @ differently depending upon where it is?
>
> others must have covered this problem..
Indeed others have - none other than T. Berners-Lee, in RFC 1738 where
the format of a URL is specified:
In addition
On 4/9/12 1:50 PM, Ed Maste wrote:
Libfetch supports a username and password in a FTP or HTTP URL, but lacks
a method to specify '@' or ':' there, as they're used as URL component
separators. I discovered this issue because I have an FTP server that
uses an email address as the username, and I c
Libfetch supports a username and password in a FTP or HTTP URL, but lacks
a method to specify '@' or ':' there, as they're used as URL component
separators. I discovered this issue because I have an FTP server that
uses an email address as the username, and I can't use fetch(1) or
libfetch against
