Henrik Nordstrom wrote:
>
> The spec (RFC 1738) is quite clear on how to interpret FTP url's.
>
> ftp://somehost/path1/path2/...
>
> Is to be interpreted at ftp to "somehost" (possibly with user info)
> then issue a CWD for each path element in the URL.
>
> Actually there is no clean support for entering directories above the
> home(start) directory, except encoding a / in the first CWD path using
> %2f or using a lot of ../../../../..., but the same goes for plain
> ftp... (encoding %2f is the recommended one)
Well then the "Parent directory" link on the page generated needs to
point to ".." rather than "/" if the current directory is concidered
to be "/"
If I go to "ftp://oskar@machine/" and click on "Parent Directory" I end up
with a recursive link...
> Have you ever tried to run ftp against a "DOS" oriented ftp server where
> you can (and have to) do
> cd e:\some\dir
Oskar
=============================================
'experience made art, but inexperience luck.'
=============================================
Received on Tue Feb 25 1997 - 07:19:19 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:34:32 MST