> Hello, > > I got this old bug about a problem with lftp and > the warftpd Daemon. I have no warftpd available > so I cannot verify this problem. > > If you tell me this is a problem with warftpd I > will close the bug report: > > http://bugs.debian.org/77866 > > "Some ftp daemons (such as the popular War-FTPD common in the Winblows world) > implement REST 1 as pointing to the start (first byte) of the file, and REST > 0 as an illegal command. > > While doing 1GB of download from a War-FTPD server (NO, it was NOT mp3 nor > warez, sheesh :-) ) I noticed many of the files were corrupted (reget was > active, and multiple connections were needed to get some of those files). > Some of the files were downloaded correctly (maybe they were retrieved in a > single connection?). > > ncftp managed to download the entire 5GB dataset safely, and it did MANY > regets to archieve it. I noticed that ncftp detects the REST stuff by trying > a REST 1 (which succeds with War-FTPD) and then a REST 0 (which fails with > War-FTPD) to detect what the other side expects REST to mean, and work > around the issue. > > I have not read the relevant RFC to verify who's at fault, but I'd really > like lftp to work with War-FTPD, as it is a very common ftp daemon." > > thx.
I may be wrong, but if I remember correctly, it was an old bug related to WarFTPD, which was work-arounded in lftp meanwhile... Just use this response as an hint to make you look into the changelog or whatever :-P (too lazy to do it now)
