Yep, Microsoft server farms are incredibly out of sync - not only timestamps can mismatch between different servers, resulting in an unneeded download, but I've seen WGET commence downloading of
mpam-fe because of mismatching file size on the server, and then the downloaded remote file turned out to be exactly the same size as existing local file!
That was apparently from the same server and reusing the same connection:
- Code: Select all
--2016-11-01 02:41:02-- http://download.microsoft.com/download/DefinitionUpdates/mpam-fe.exe
Resolving download.microsoft.com... 84.53.167.128
Connecting to download.microsoft.com|84.53.167.128|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 130854680 (125M) [application/octet-stream]
The sizes do not match (local 130866960) -- retrieving.
--2016-11-01 02:41:11-- http://download.microsoft.com/download/DefinitionUpdates/mpam-fe.exe
Reusing existing connection to download.microsoft.com:80.
HTTP request sent, awaiting response... 200 OK
Length: 130866960 (125M) [application/octet-stream]
Saving to: `../client/msse/x86-glb/mpam-fe.exe'
100%[==============================================================================>] 130,866,960 11.3M/s in 11s
2016-11-01 02:41:22 (11.1 MB/s) - `../client/msse/x86-glb/mpam-fe.exe' saved [130866960/130866960]