Hello, Still troubleshooting through an uncooperative proxy, here. :/ This time it's an FTP proxy rather than doing FTP-over-HTTP. The proxy is dropping the ball on MDTM, not the remote server (I did get the remote sysadmin to upgrade Cerberus :)
I had thought that if lftp receives an unuseful response to MDTM, while mirroring, that it would fall back to using the LIST output for date information. However the trace below shows that it just quits. Is this expected behavior? > lftp -c "open 11.22.33.44; mirror 'logs/77/'" ---- Resolving host address... ---- 1 address found: 192.168.1.1 ---- Connecting to proxy foo (192.168.1.1) port 21 <--- 220- <--- 220- FTP Proxy Service <--- 220- <--- 220- INSTRUCTIONS <--- 220- <--- 220- Enter [EMAIL PROTECTED] below to connect to host <--- 220- 'server' as user 'login'. <--- 220 ---> USER [EMAIL PROTECTED] <--- 331-(----GATEWAY CONNECTED TO 11.22.33.44----) <--- 331-(220-Cerberus FTP Server Personal Edition) <--- 331-(220-UNREGISTERED) <--- 331-(220-Welcome to Cerberus FTP Server) <--- 331-(220 Created by Grant Averett) <--- 331 User anonymous, password please ---> PASS lftp@ <--- 230 Password Ok, User logged in ---> FEAT <--- 500 command not understood ---> PWD <--- 257 "/" is the current directory ---> CWD /logs/77 <--- 250 Change directory ok ---> PASV <--- 227 Entering Passive Mode (192,168,1,1,170,64) ---- Connecting data socket to (192.168.1.1) port 43584 ---- Data connection established ---> LIST <--- 150 Opening data connection ---- Got EOF on data connection ---- Closing data socket <--- 226 Transfer complete ---> TYPE I <--- 200 Type Binary ---> MDTM XML_SCRIPT.XML <--- 500 command not understood ---> QUIT ---- Closing control socket Curran Schiefelbein
