Skip to main content
Tweeted twitter.com/ServerFault
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

I just updated a bug report on meta.SE about excessive caching:

Caching should not show me yesterday's info!Caching should not show me yesterday's info!

I would like to know how many votes I've cast, but I'm still seeing yesterday's vote counts. Based on the other times I've noticed this, I'm going to continue to see yesterdays's counts for quite a while.

Would a request from a/the mod(s) be able to get the caching turned down a bit?

I just updated a bug report on meta.SE about excessive caching:

Caching should not show me yesterday's info!

I would like to know how many votes I've cast, but I'm still seeing yesterday's vote counts. Based on the other times I've noticed this, I'm going to continue to see yesterdays's counts for quite a while.

Would a request from a/the mod(s) be able to get the caching turned down a bit?

I just updated a bug report on meta.SE about excessive caching:

Caching should not show me yesterday's info!

I would like to know how many votes I've cast, but I'm still seeing yesterday's vote counts. Based on the other times I've noticed this, I'm going to continue to see yesterdays's counts for quite a while.

Would a request from a/the mod(s) be able to get the caching turned down a bit?

Source Link

Is there anything site-specific that can be done about excessive caching?

I just updated a bug report on meta.SE about excessive caching:

Caching should not show me yesterday's info!

I would like to know how many votes I've cast, but I'm still seeing yesterday's vote counts. Based on the other times I've noticed this, I'm going to continue to see yesterdays's counts for quite a while.

Would a request from a/the mod(s) be able to get the caching turned down a bit?