On Wed, Apr 19, 2006 at 10:04:36PM -0400, matthew sporleder wrote:
> For a while now, when I try to use http for sysinstall, I run into
> some annoying bugs.
> 
> For example:
> I say my sets are at http://10.0.0.1/~msporleder/
> 
> I say my host is 10.0.0.1
> my base dir is ~msporleder
> and my sets dir is /sets
> 
> I blank out the user/password (defaults to ftp)

You don't want to do that....
Leave it as "ftp" for anonymous access.
(maybe the code could check for empty strings as well)

> and my url ends up as: http://%20@10.0.0.1/%7Emsporleder/sets//
> 
> I understand the control characters, but why do they show up at all?

The %20 is a space, possibly from the 'emptied' username/password.
Although the code is trying to generate http://<user>:<password>@<host>/...

The %7E is ~ which is (by strict reading of RFC 1738) unsafe in a URL.

> Also, why is sysinstall translated them?  ftp from the command line
> works with the real url (symbols and all)

Because they aren't legal in a URL

> Also, why is the (outdated) user@psasword url structure forced?

It uses user:password@host unless user is "ftp" and the password is blank.

	David

-- 
David Laight: david@l8s.co.uk