https://bugzilla.novell.com/show_bug.cgi?id=179623 ------- Comment #14 from jsrain@novell.com 2007-03-06 05:39 MST ------- The last example is incorrect and the URL is really corrupted. The previous ones are correct. Note that it is essential that URL with absolute path contains the leading slash encoded. See the details from RFC below. I will fix the behavior in case of multiple slashes, that's the only bug which is present. The RFC1738 (http://rfc.net/rfc1738.html) defines in Section 3.2.2., how the url-path component has to be interpreted in the FTP scheme. "[...] 3.2.2. FTP url-path The url-path of a FTP URL has the following syntax: <cwd1>/<cwd2>/.../<cwdN>/<name>;type=<typecode> Where <cwd1> through <cwdN> and <name> are (possibly encoded) strings and <typecode> is one of the characters "a", "i", or "d". The part ";type=<typecode>" may be omitted. The <cwdx> and <name> parts may be empty. The whole url-path may be omitted, including the "/" delimiting it from the prefix containing user, password, host, and port. The url-path is interpreted as a series of FTP commands as follows: Each of the <cwd> elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. [...] Within a name or CWD component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. [...]" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.