On Mon, Aug 21, 2000 at 11:02:30PM +0100, Robert de Bath wrote:
> > STAT is only used for FXP. So it is not a problem for normal operation.
> > restarting STOR is a wanted feature, but client cannot find out if server
> > is broken in regard to REST/STOR.
> They could, but it'd be a horrible (and slow!) hack.
Indeed, by reading the uploaded file and comparing it with original one.
> > > Some 'doze daemons don't do pasv but the only UNIX ones that fail
> > > are behind firewalls and give IP's like 10.0.0.5. (from rfc1597)
> >
> > lftp can be taught about such addresses to switch to PORT automatically,
> > I'll try to do that.
> Perhaps; but remember if lftp is being used internally those IP addresses
> may be correct and reachable.
Yes, I did not forget that :). I wonder, if those servers are behind firewall,
then how can outsider connect to them? Maybe it is better just to connect
to original server address and specified in reply port?
> > I don't want to make too complex workaround procedures for broken
> > servers anyway. Why not write to authors of those servers?
> Oh I do, not that it does much good; they often don't care and even when they
> seem to there's a good chance it doesn't get fixed.
I don't quite understand why people install such a bad and
unmaintained software...
How much servers do you know which are running GuildFTP?
> You're definitly right about work for the evil servers; in fact in your
> shoes I'd be very tempted to get rid of those 'compatibility' flags and
> just have few states (Perfect, Fast, Poor, Evil) to control the features.
It is not hard to add simple settings. Those Poor/Evil are just sets
of simple settings.
> In fact that sounds like quite a good idea for some macros ...
> alias fast "source ~/.lftp/fast"
good idea.
> Hmm; lftp> on regex(resp220, "GuildFTP") do source ~/.lftp/evil
> Naaaa. :-)
That's way too complex.
--
Alexander. | http://www.yars.free.net/~lav/
