On the subject of cache-timeout alteration, the company maintains that they are absolutely not altering those settings for pages which are loaded through the service. Moreover, when there is content being loaded which they serve directly they are setting the cache option to a "no-cache; must-revalidate" setting which should force all modern browsers to pull a fresh copy of the data every time. Because the claims about the cache alteration came from a 3rd party which they haven’t been able to validate there isn’t a lot more to go on here as to what actually happened. We are left with something of a he said, she said sort of situation. Still, knowing that the service shouldn’t be altering the cache setting is somewhat reassuring.
Never miss another post: Sign up for email alerts and get only the content you want direct to your inbox.