Henrik Nordstrom wrote: > >> So if, for example, the admin wanted to define & as the alternative >> separator, ftp://me&myhost:[EMAIL PROTECTED]/ would be a little less >> ambiguous >> to browser-style schemas. > > Sounds reasonable. Except that it's quite impractical to use in HTML > coding and very many applications (and users) rendering data into HTML > will get it wrong..
You (the admin) would elect the alternate separator. > Note: how most browser user agents implements the ftp:// URI scheme in > general is quite far outside the standards, so it's not easy to know > what will happen when trying something other than plain anonymous ftp > with non-problematic characters, or even file paths.. Of course - most do and I wouldn't count on consistency.
