Cache problem with activity page
It seems there is a cache problem with the activity page, and it occurs on both Firefox and IE. If I make some code modifications in the activity view, I first have to empty the cache before i can see any change.
Why is this happening only in the activity page, and how could I fix it?
#1 Updated by Felix Schäfer over 10 years ago
- Status changed from New to Closed
- Resolution set to Invalid
This is expected behavior: the activity page being one of the most visited and "easiest" to decide if it needs refreshing or not, the page is served with an ETag (the requesting browser says "I'd like the activity page, but I already have one with the ETag SOMETHING" and the app responds "oh, then you already have the newest version of the page, you're good", the server doesn't generate a view or anything else in that case). You should deactivate the cache of your client (which you should do when developing anyway).