Last modified: 2013-04-12 19:46:02 UTC
If you revisit a page you've recently seen, it shows the same notification count as when you last visited the page. The count itself is generated as part of the page (not pulled from JS), and since the cache headers of the page aren't supposed to allow caching, I'm not sure why this bug exists. The cache headers for each page are: Cache-Control private, must-revalidate, max-age=0 Expires Wed Dec 31 1969 16:00:00 GMT-0800 (PST) Shouldn't that prevent the page from being cached by the client? Steps to reproduce: 1. Load the Main Page and note what the notification count is 2. Perform some action that generates a notification for yourself (for example, leave a talk page message with another account) 3. Soft-refresh the Main Page You'll see that the notification count is still the same. If you hard-refresh the page, however, it will update the count.
I should mention this bug only affects logged in users (only logged in users can receive notifications).
*** This bug has been marked as a duplicate of bug 44056 ***