[Top][All Lists]

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

[Bug-wget] WGET bug with --timestamping

From: Jay Pellam
Subject: [Bug-wget] WGET bug with --timestamping
Date: Thu, 04 Dec 2008 13:59:41 -0500

Confirmed in 1.10.1, the latest binary Windows build I've found.
Was also in 1.8.2, the previous Win32 version I have.

Contrary to what the help says (--timestamping: don't re-retrieve files unless 
newer than local), WGET re-retrieves the file and overwrites a NEWER file if 
the sizes are different.

        Resolving img47.imageshack.us...
        Connecting to img47.imageshack.us||:80... connected.
        HTTP request sent, awaiting response... 200 OK
        Length: 60,988 (60K) [image/jpeg]
        The sizes do not match (local 45025) -- retrieving.

To me this seems clearly wrong.  There is no question that its wrong when the 
performance is compared to the documentation.  I could understand why you might 
not want to change this behavior absolutely but if not a new switch should be 
provided, eg, --ignoresize.

For the documented purpose (mirroring) it seems like it could be disasterous in 
many situations.

reply via email to

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