Justin Piszcz | 18 May 2010 14:08

lftp 4.0.7 reconnect bug

Hi,

How do I avoid this?
  at 0 (0%) [Delaying before reconnect: 3093850488667]

I've tried setting everything to 0:
set net:reconnect-interval-base 0
set net:reconnect-interval-max 0
set net:reconnect-interval-multiplier 0

I've tried lowering the defaults:
et net:reconnect-interval-base 60
set net:reconnect-interval-max 60
set net:reconnect-interval-multiplier 1

But, eventually, this happens: 3093850488667

Any ideas?

Justin.

Alexander V. Lukyanov | 20 May 2010 15:50
Picon
Gravatar

Re: [patch] RFC 2640 compliance

On Thu, Apr 29, 2010 at 05:37:18PM +0800, Henry Hu wrote:
> However, lftp still issues a "LANG" command after the FEAT response.
> When it receives the response of LANG, it sets encoding to UTF-8.

According to the same RFC2640 (4.1 The LANG command):
                                           Once negotiated, server-PI
   MUST return server messages and textual part of command responses in
   the negotiated language and encoded in UTF-8.

Also (3.2 Servers compliance):

   - Servers MUST support the UTF-8 feature in response to the FEAT
     command [RFC2389].

So your server does not completely comply to RFC2640 too.

> Since the server uses GBK in fact, the filenames in Chinese are
> garbled.
> Since there's such passage in RFC 2640:
>    - Clients MUST support the FEAT command and recognize the "UTF8"
>      feature (defined in 3.2 above) to determine if a server supports
>      UTF-8 encoding.
> So I think that lftp should check that if UTF8 is supported, and if
> true, set the connection encoding to UTF8.
> I made such a patch:

I'll apply this patch as it only affects non-compliant servers.
Thank you!

> And it works correctly here, with ProFTPd.
(Continue reading)

Eric Terpening | 6 May 2010 06:35
Picon

Re: lftp

Hi

I humbly suggest that you add HTTP pipelining support to lftp.

I think this would be a great feature.

FreeBSD portsupdate (phttpget) and aria2c have implemented it, and
libcurl has some support for it; even Mozilla has added it.

Knowing lftp's superior design and performance, I think lftp's
implementation would be the best.

Cheers,
Eric

On 9/25/09, Alexander V. Lukyanov <lav <at> netis.ru> wrote:
> On Fri, Sep 25, 2009 at 02:51:17PM +1200, Eric Terpening wrote:
>> 2- make lftp timeout and disconnect after a period of time, e.g.
>> download a file for 60 seconds and then stop?
>
> at now+60seconds -- exit kill &
>
> This will terminate lftp in 60 seconds. If you want to stop a transfer
> and close connection without exiting, then this would do:
>
> get file &
> at now+60seconds -- "kill 0; close" &
>
> --
>    Alexander..
(Continue reading)

Daniel Fazekas | 20 May 2010 17:21
Picon

Re: lftp and features

On Apr 26, 2010, at 10:48, Thomas Samoht wrote:

> 1. When using AUTH TLS, I can see PBSZ 0 and PROT P. I haven't read the RFC, but I hope this means that
> both command, and data channel are encrypted. Am I correct?

Not necessarily, that depends on the ftp:ssl-protect-data option.

set ftp:ssl-protect-data yes

if you want to encrypt the data channel too. It is off by default.
You'll probably want ftp:ssl-force too, and set up certificate verification for the server to make sure
you're really talking to the server you think you do.

Search for "ftp:ssl" in the man page for more information.

You can also limit these settings to the given site only:
set ftp:ssl-force/ftp.example.com yes

> 2. Is there a way to store "user/password" combinations somewhere in a file and only use a passphrase to
that file
> for authentication (like with SSH), e.g.

You can use the standard .netrc file like any other ftp client, or set up bookmarks in ~/.lftp/bookmarks.
These are of course plain text files with the password also stored in plain text though.

Search for "bookmark" in the man page.

> 4. When I use the mirror -R, I can see the following behaviours. Correct me, if I'm wrong.
> If the file is present, and it is the same then the one on the local site, nothing is transferred.

(Continue reading)


Gmane