How do I prevent a cached page from being served when the user clicks the back button?

Using the back button will use the cache as @kindall said. It really depends on what you don't want cached Instead of encouraging users from using the back button can you structure the page navigation so that the user can always get to where they want without having to use a back button? The stuff you don't want cached can you load it dynamically via ajax?

Using the back button will use the cache as @kindall said. It really depends on what you don't want cached. Instead of encouraging users from using the back button can you structure the page navigation so that the user can always get to where they want without having to use a back button?

The stuff you don't want cached can you load it dynamically via ajax?

Answering my own question. As it turns out, setting the following response headers (as opposed to META tags) worked for me: Cache-Control private, no-store, max-age=0, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma no-cache Expires Fri, 01 Jan 1990 00:00:00 GMT If you're working in Rails like I am, you can do this easily by putting the following in an ApplicationController before_filter callback: response. Headers"Cache-Control" = "private, no-store, max-age=0, no-cache, must-revalidate, post-check=0, pre-check=0" response.

Headers"Pragma" = "no-cache" response. Headers"Expires" = "Fri, 01 Jan 1990 00:00:00 GMT.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.