On Tue, Nov 25, 2003 at 12:39:32AM +0100, Gisle Vanem wrote: > An url like this ftp://giva:[EMAIL PROTECTED]/home/2/kunder/giva/ all of > a sudden has started producing crap like this: > > O'.O'..O' .sshN?O'.tinN?O'MailN?O'NewsN?O'mailN?O' www_siderO'zipi]' > .newsrcW]'.pine-debug1^]'.pine-debug2_]'.pine-debug3`]'. > > (i.e. the contents of the inode AFAICS). I discovered Lynx is sending > "RETR /home/2/kunder/giva" and not a CD followed by a LIST. > ftp://giva:[EMAIL PROTECTED]/~giva/ also does a "RETR ~giva". > > Looking at htftp.c trying to determine how Lynx detects if it's a > dir or file, didn't make me any wiser. How can the above URL be a > plain file? Shouldn't Lynx try CD/LIST first, then RETR maybe? > > AFAICR, RETR used to fail on my ISP in this case, so Lynx > tried a LIST. But now RETR doesn't fail, but produces the above > garbage. How do I fix this? > > Tested with Lynx 2.8.5 dev.16 on both MingW and djgpp. > My ISP identifies itself with "220 FTP proxy (v0.13.4) ready" > in the banner and "215 UNIX Type: L8 Version: BSD-199506" > in response to the SYST.
This doesn't appear to be the same case as the broken ProFTPD. I'm not sure how to analyze it. -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
