Re: Status of RFC 1738 -- 'ftp' URI scheme

Dan B. scripsit:

> For example, I was surprised when I found that ftp://U@host/x didn't
> refer to the same file as ftp://host/x (at least in Seamonkey (I think)
> and a particular FTP server).

Yes, so was I.  I think it's quite independent of the FTP server.

I struggled for a while to find a portable URI pattern that would solve
this problem, and finally chose to create a symbolic link "root" in my
home directory that points to /.

> (I don't recall whether I checked whether ftp://U@host//x referred to
> the same thing as ftp://host/x .)

Sometimes yes, sometimes no, is my recollection.

> However, if the mapping from the URI path to the FTP is defined to
> involve stripping off the leading URI path slash, then FTP pathnames
> of "x" vs "/x" can be differentiated (as ftp://U@host/x vs.
> ftp://U@host//x, respectively).  Apparently, that's how Seamonkey
> (and maybe wget) treats it.

But not Chrome.

John Cowan
"The exception proves the rule."  Dimbulbs think: "Your counterexample proves
my theory."  Latin students think "'Probat' means 'tests': the exception puts
the rule to the proof."  But legal historians know it means "Evidence for an
exception is evidence of the existence of a rule in cases not excepted from."

Received on Tuesday, 18 January 2011 18:22:23 UTC