Hey Thomas,
the implementation of MDTM seems to straight forward. I possibly find
some time during the next weekends.
I'll discuss the backwards compatibility issue with Darshit (also wget
maintainer).
Regards, Tim
On 6/2/24 17:40, Thomas Orgis wrote:
Am Sun, 2 Jun 2024 13:44:50 +0200
sch
Am Sun, 2 Jun 2024 13:44:50 +0200
schrieb Tim Rühsen :
> And normally (or often), you don't need the server timestamp for single
> file downloads. And if you really do, there is -N.
Well, what 'normal' need is is obviously something one can discuss
endlessly (see https://bugzilla.mozilla.org/sh
On 6/1/24 20:33, Thomas Orgis wrote:
Hi Tim,
Am Sat, 1 Jun 2024 18:57:00 +0200
schrieb Tim Rühsen :
Wget sets the remote time when using the -N / --timestamping option.
Hm, that is related to comparing local and remote timestamps for
deciding to re-download a file or not (I read in the man p
Hi Tim,
Am Sat, 1 Jun 2024 18:57:00 +0200
schrieb Tim Rühsen :
> Wget sets the remote time when using the -N / --timestamping option.
Hm, that is related to comparing local and remote timestamps for
deciding to re-download a file or not (I read in the man page). How is
that related to wget not
Hey Thomas,
thanks for your report.
Wget sets the remote time when using the -N / --timestamping option.
> Is a fix in wget 1.x something to be considered at this point in time?
Yes, if we find a volunteer to make up a patch.
> FTP support seems to be dropped altogether from Wget 2 (correct?)
Hi all,
I noticed that while wget does nicely preserve Last-Modified times from
HTTP downloads, it does not do so for FTP, apparently. The example I see
is the upstream archive of the file tool:
ftp://ftp.astron.com/pub/file/file-4.26.tar.gz
Wget correctly parses the time information:
$
