Hi, perhaps anyone of you can explain me the following: I tried to WGet a file from my local FTP-Server - don't ask me why :-) WGet v1.7-dev 2001/02/16 (with ssl support) for Win32 Serv-U v2.5e for Win32 ------------------ WGet Output Start --------------------- D:\>wget -d http://guest:[EMAIL PROTECTED]:2100/ DEBUG output created by Wget 1.7-dev on Windows. parseurl ("http://guest:[EMAIL PROTECTED]:2100/") -> host 127.0.0.1 -> port 2100 - > opath -> dir -> file -> ndir newpath: / --18:23:35-- http://guest:<password>@127.0.0.1:2100/ => `index.html.3' Connecting to 127.0.0.1:2100... Created fd 36. connected! ---request begin--- GET / HTTP/1.0 User-Agent: Wget/1.7-dev Host: 127.0.0.1:2100 Accept: */* Connection: Keep-Alive Authorization: Basic Z3Vlc3Q6Z3Vlc3Q= ---request end--- HTTP request sent, awaiting response... 220-Serv-U FTP-Server v2.5e for WinSock ready... Closing fd 36 18:23:35 ERROR -1: Malformed status line. ------------------ WGet Output End --------------------- So I tried the usual console FTP: ------------- Console FTP Output Start --------------- D:\>ftp Ftp> open localhost 2100 Verbindung mit arcticblue. 220-Serv-U FTP-Server v2.5e for WinSock ready... 220-Welcome to ArcticBlue. 220- <some more text here> 220- 220-Have Fun! 220- 220 Benutzer (arcticblue:(none)): guest 331 User name okay, need password. Kennwort: 230 User logged in, proceed. Ftp> dir 200 PORT Command successful. 150 Opening ASCII mode data connection for /bin/ls. -rwxrwxrwx 1 user group 20480000 Mar 5 14:59 1.r00 226 Transfer complete. Ftp: 62 Bytes empfangen in 0.00Sekunden 62000.00KB/Sek. Ftp> ------------- Console FTP Output End --------------- As you can see this worked perfectly. My first thought was the startup message, but then I tried another FTP-Server (ftp.leo.org) which also has a startup-msg and that worked fine with WGet. Any hints? bye GoTo
