Quote:
Originally Posted by theducks
What about just using the alternate site listed on the download page?
|
@
theducks, I think the problem is downstream from the download source. It seems that if 'they' have something in 'their' download cache from the same source, with a
similar name, and
same size, that the same destination got some time before, then they send what's in 'their' cache with the new name rather than doing the download.
I've realised that 'they' cant verify by checksum because that's not available at the start of a download.
Most of us don't have a 'download optimizer' between us and the download site, thats why its only effecting a few folks. It maybe the ISP or it may be a 'them' that offers an 'optimized download service' to ISP's
Why is this happening on MSI files, maybe because this weeks MSI file is more likely to be the same size as last weeks, than a DMG or a TAR, or that 85% of downloads are MSI's.
One certain solution would be to make sure that successive install files, are not the same size. Or we all start running from source
@
e...w - would HTTPS change the source, file name, file size, or destination, and if not, then how would it solve the problem ?
BR