[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] problem with --continue and already completed ftp downloa

From: Paul Wratt
Subject: Re: [Bug-wget] problem with --continue and already completed ftp downloads
Date: Wed, 30 Nov 2011 09:49:28 +1300

I have had this problem in the past. I should be more intelligent
about the use of "--continue"

According to your output, it could either compare REST again 213, or
rather notify (not stop) because of "504 Reply marker must be 0"

A note here for Eike regarding the use of --continue with *.ZIP, its
redundant unless wget last quit halfway through a download. wget has
"auto-continue" on by default and will retry X times (maybe 4/5 or 20,
cant remember off hand) which can also be changed/set on command line


On Wed, Nov 30, 2011 at 1:58 AM, Eike Kohnert <address@hidden> wrote:
> Hi all,
> i use wget to download a complete directory from a ftp server and want to
> download new files every day.
> I use a command like
> wget --continue ftp://someserver/somedirectory/*.ZIP
> It seems like wget tries to resume files, even if they are already finished.
> I sniffed the generated network traffic and found something like this:
> 213 872953
> 227 Entering Passive Mode (....).
> REST 872953
> 504 Reply marker must be 0.
> I think wget should not do the REST command because the retrieved size
> equals the size of the already downloaded file. So the resuming download
> would download only the remaining 0 bytes which does not make much sense. On
> servers which do not support resume this will cause the whole file being
> downloaded again.
> I used wget version 1.12
> Best regards
> Eike

reply via email to

[Prev in Thread] Current Thread [Next in Thread]