I have been working on a problem to prevent serving cached server pages on click of browser back button. Went thru This question and setting appropriate response headers (below) work, but there is inconsistent behavior between IE and chrome.
response.setHeader("Cache-Control", "no-cache, no-store, must-revalidate");
response.setHeader("Pragma", "no-cache");
response.setHeader("Expires", "0");
IE: Serves a 'Webpage has expired' once I go back to a page using back button
Chrome: Doesn't say page expired, and doesn't serve a cached page either, but does a new server request even on a back button - sort of like hitting refresh.
My question: Is this how they are meant to respond to the headers and is there a way to achieve a consistent result? The primary intention is to avoid serving cached pages on back button across browsers.
