View Single Post
Old 05-20-2017, 01:22 AM   #20
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 49,862
Karma: 176799834
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by petercreasey View Post
Okay, then there should not be any sources of the bad update lingering around for unsuspecting updaters!?!
When I look at my firmware downloads, the file is served by an Akamai edge server. This reduces the load on Kobo's servers and you get the data from a source that is geographically closer to you. The problem is that like any caching proxy, it is possible for the data served by Akamai to be out of date. I suspect that Kobo would have sent Akamai a purge request for the bad firmware update file as soon as they knew about the problem but that would still take some time to be processed.
DNSB is offline   Reply With Quote