From: Hrvoje Niksic
> Prepending is already there,
Yes, it certainly is, which is why I had to disable it in my code for
VMS FTP servers.
> and adding it fixed many problems with
> FTP servers that log you in a non-/ working directory.
Which of those problems would _not_ be fixed by my two-step CWD for a
relative path? That is:
1. CWD to the string which the server reported in its initial PWD
response.
2. CWD to the relative path in the URL ("A/B" in our current
example).
On a VMS server, the first path is probably pure VMS, so it works, and
the second path is pure UNIX, so it also works (on all the servers I've
tried, at least). As I remark in the (seldom-if-ever-read) comments in
my "src/ftp.c", I see no reason why this scheme would fail on any
reasonable server. But I'm always open to a good argument, especially
if it includes a demonstration of a good counter-example.
This (in my opinion, stinking-bad) prepending code is the worst part
of what makes the current (not-mine) VMS FTP server code so awful.
(Running a close second is the part which discards the device name from
the initial PWD response, which led to a user complaint in this forum a
while back, involving an inability to specify a different device in a
URL.)
------------------------------------------------------------------------
Steven M. Schweda (+1) 651-699-9818
382 South Warwick Street [EMAIL PROTECTED]
Saint Paul MN 55105-2547
