This is probably a bad idea to force this behavior, because the user expects to see what he saw before, and not an updated view. If this is the behavior of Chrome / Firefox / Safari, then, apparently, users want this behavior because they chose this browser. If they want to update the presentation, they can update themselves.
However, I often see that this is done with Javascript in the browser. You can connect to page load events and refresh manually if the second page loads. But if the client uses noscript or otherwise does not support Javascript, you're out of luck. Also, be careful to reload correctly so that users donβt get to a new page every time they click βBackβ and get stuck in a battle of quick clicks.
source share