Here's a recipe for confusion:

  1. Load a page on Stack Exchange.

  2. Do anything that updates the page via JS―leave a comment, vote, etc.

  3. Leave the page by following a link.

  4. Use the browser's back button to return to the original page.

You'll be unpleasantly surprised to find that all the updates from step 2 are gone. This is really confusing, and it wasn't true two weeks ago. It's a major usability problem. I assume it's due to the Cache-Control header changes, since I first noticed the problem on either August 5 or 6.

Leave a comment, click a link, go back, and the comment is gone.

Stack Exchange used to provide users with updated pages without making them hit the reload button all the time. Now several times each day I have to figure out the page is out of date on my own and hit reload. It's confusing every single time.

Please fix my back button!

  • 1
    I've been noticing this over the last couple of days too. Using Firefox 31.0.
    – JonK
    Aug 19 '14 at 18:13
  • 2
    This has been the case for eons, certainly in Chrome. The cache headers have been changed to prevent public caches (proxy servers) from caching the response, and the browser has been instructed not to cache the page at all now. Aug 19 '14 at 18:21
  • 1
    See Ajax, back button and DOM updates for example, from 2009. The behaviour you claim changed only recently, has been the status quo for years now, because Stack Overflow pages use a beforeunload event handler. Aug 19 '14 at 18:26
  • @MartijnPieters Oh, it's too bad it was always broken in Chrome. That must be irritating for Chrome users.
    – user215040
    Aug 19 '14 at 18:34
  • The back button has been broken in so many web applications for so long that I seldom use it anymore. I just assume that it won't work.
    – user102937
    Aug 19 '14 at 18:51
  • Just checking what happens to this. Can't repro using Firefox. BTW, what's Chrome?
    – 0xdeadbeef
    Aug 19 '14 at 19:17
  • @0xdeadbeef lenntech.com/periodic/elements/cr.htm Aug 20 '14 at 9:06
  • Even though this was never fixed, I've gotten used to it, so it doesn't seem like a big deal anymore. I just give SE lots of extra reloads these days.
    – user215040
    Aug 3 '15 at 4:11

OK; I'm trying a slightly different configuration - that no-cache was perhaps too aggressive. This should be here on meta in about 10 minutes.

You must log in to answer this question.