My only concern about only checking modification date is when there is an incomplete download, the local modification date is set to the current time. So when the mirror is next attempted, the file is marked newer than the server file and is not replaced. Is there some way to make the local modification date (time_t = 0 ) until it is finished?? This way the incomplete file will always be older than the server file, and will be replaced.
Craig
From: Hrvoje Niksic <[EMAIL PROTECTED]> To: "Craig Sowadski" <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: wget-cvs-ifmodsince.patch Date: Thu, 26 Feb 2004 00:44:48 +0100
"Craig Sowadski" <[EMAIL PROTECTED]> writes:
> 1. I can implement a patch like my original that only uses the > if-modified-since when the last-modified field is excluded from the > head-only request.
Isn't that what your most recent patch implements?
> 2. Send the if-modified-since request, then get header to check for > size only if the if-modified-since request sends back a "304 - not > modified"
That means introducing an additional hop for unchanged files. This is in a way even worse because I'd expect them to be in the majority.
> 3. implement a separate time-stamping and file-size checking > options.
This might make the most sense. Or, we could completely ignore the file size issue and simply trust what If-Modified-Since tells us.
I guess I'd like for time-stamping to use If-Modified-Since, period. That's what it's for, and the Last-Modified thing has always been a weird hack that somehow survived the times. What do the others think about this?
_________________________________________________________________
Find and compare great deals on Broadband access at the MSN High-Speed Marketplace. http://click.atdmt.com/AVE/go/onm00200360ave/direct/01/
