Your message dated Mon, 02 Aug 2010 13:15:22 +0200
with message-id <[email protected]>
and subject line Re: #402652 lftp: handle 500 'ALLO' server response
has caused the Debian Bug report #402652,
regarding lftp: handle 500 'ALLO' server response
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
402652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402652
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lftp
Version: 3.5.6-1
Severity: minor
Hello,
Since version 3.5.0, lftp supports the ALLO command. Its use is
enabled by default. Lftp however ignores the reply from the server.
This breaks passive-mode transfers when the ALLO command is not
supported by the server (see the connection traces below).
I think that lftp should try to handle the error code from the server,
and either inform the user of the failed operation, or retry without
the ALLO command.
I know that the default behavior can be changed with the ftp:use-allo
variable (that is why I set the bug severity to minor), but it is not
a problem easy to diagnose.
Regards,
Arnaud Giersch
Some connection traces with ftp:use-allo set to true. When it is set
to false, all is working fine.
* FTP in normal mode:
lftp [email protected]:/> set ftp:passive-mode false
lftp [email protected]:/> put toto
---> PORT 192,168,1,1,160,18
<--- 200 PORT command successful.
---> ALLO 0
<--- 500 'ALLO': command unrecognized.
---> STOR toto
---- Closing data socket
<--- 150 Opening BINARY mode data connection for toto
<--- 226 Transfer complete.
* FTP in passive mode:
lftp [email protected]:/> set ftp:passive-mode true
lftp [email protected]:/> put toto
---> PASV
<--- 227 Entering Passive Mode (212,27,63,3,147,252).
---- Connecting data socket to (212.27.63.3) port 37884
---- Data connection established
---> ALLO 0
---- Closing data socket
<--- 500 'ALLO': command unrecognized.
---> STOR toto
<--- 425 Can't open data connection.
---> PASV
<--- 227 Entering Passive Mode (212,27,63,3,179,239).
---- Connecting data socket to (212.27.63.3) port 46063
---- Data connection established
---> ALLO 0
---- Closing data socket
<--- 500 'ALLO': command unrecognized.
---> STOR toto
<--- 425 Can't open data connection.
...
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15)
Versions of packages lftp depends on:
ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries
ii libexpat1 1.95.8-3.3 XML parsing C library - runtime li
ii libgcc1 1:4.1.1-19 GCC support library
ii libgcrypt11 1.2.3-2 LGPL Crypto library - runtime libr
ii libgnutls13 1.4.4-3 the GNU TLS library - runtime libr
ii libgpg-error0 1.4-1 library for common error values an
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libreadline5 5.2-1 GNU readline and history libraries
ii libtasn1-3 0.3.6-2 Manage ASN.1 structures (runtime)
ii netbase 4.27 Basic TCP/IP networking system
ii zlib1g 1:1.2.3-13 compression library - runtime
lftp recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Samedi 31 juillet 2010, vers 21:50:43 (+0200), Noël Köthe a écrit :
> I'm trying to reproduce your bugreport http://bugs.debian.org/402652
> with proftp as server but it doesn't support the ALLO.
> Can you tell me with which server you can reproduce the problem?
Hi Noël,
I experienced the problem with my ISP's server, but I have no idea which
software it is. Today, with the current lftp version, I am not able to
reproduce the problem anymore.
I spent some time compiling older versions of lftp, and the problem
seems to be fixed since version 3.5.13.
I am therefore closing the bug.
Regards,
Arnaud
--- End Message ---
