-
In the glorious olden days of a week ago, usercp would be refreshed every time I clicked on the relevant navigation button. Now "updates" just reloads from cache when I hit the "following" button, so I have to F5 every time to see what is actually new. Same with threads, so when I just F5ed the "updates" and saw that there was a new post in the helmets thread, clicking on the thread title reloaded the page from the cache so I had to F5 that too in order to see the new post.
There is no cache on the API.
There is no cache on the web pages.
The updates page is not cached.
Any collection you see on any page is not cached.The caching strategy of Microcosm is only ever to cache single items (one comment) and never to cache any collection (a page that lists things... such as the updates page).
We even send API headers to say to the client (the web app you're using) to never ever cache anything.
Then we send headers from the web app, saying that the web pages should never ever be cached.
I think the only place where anything should be remembered by the browser is that files are aggressively cached (images, avatars, etc), and that redirects (old vBulletin URLs) are 301'd (permanently moved).
Nothing is cached... any other behaviour your browser is doing and you have control over via your browser settings.
Since I'm so full of
hate and biletoast and marmalade this morning, one more thing:In the glorious olden days of a week ago, usercp would be refreshed every time I clicked on the relevant navigation button. Now "updates" just reloads from cache when I hit the "following" button, so I have to F5 every time to see what is actually new. Same with threads, so when I just F5ed the "updates" and saw that there was a new post in the helmets thread, clicking on the thread title reloaded the page from the cache so I had to F5 that too in order to see the new post.