How to prevent browser page caching in Rails

问题:

Ubuntu -> Apache -> Phusion Passenger -> Rails 2.3

The main part of my site reacts to your clicks. So, if you click on a link, it will send you on to the destination, and instantly regenerate your page.

But, if you hit the back button, you don\'t see the new page. Unfortunately, it\'s not showing up without a manual refresh; it appears the browser is caching it. I want to make sure the browser does not cache the page.

Separately, I do want to set far-future expiration dates for all my static assets.

What\'s the best way to solve this? Should I solve this in Rails? Apache? Javascript?

Thanks for all your help, Jason

---

Alas. Neither of these suggestions forced the behavior I\'m looking for.

Maybe there\'s a javascript answer? I could have rails write out a timestamp in a comment, then have the javascript check to see if the times are within five seconds (or whatever works). If yes, then fine, but if no, then reload the page?

Do you think this would work?

Thanks for all your help,

Jason

回答1:

Finally figured this out - http://blog.serendeputy.com/posts/how-to-prevent-browsers-from-caching-a-page-in-rails/ in application_controller.rb

class ApplicationController < ActionController::Base

before_filter :set_cache_headers

  private

  def set_cache_headers
    response.headers[\"Cache-Control\"] = \"no-cache, no-store\"
    response.headers[\"Pragma\"] = \"no-cache\"
    response.headers[\"Expires\"] = \"Fri, 01 Jan 1990 00:00:00 GMT\"
  end
end

回答2:

use:

expires_now()

http://api.rubyonrails.org/classes/ActionController/ConditionalGet.html#method-i-expires_now

回答3:

I have used this line with some success in the controller. It works in Safari and Internet Explorer but I haven\'t seen it work with Firefox.

response.headers[\"Expires\"] = \"#{1.year.ago}\"

For your second point, if you use the the rails helper methods like

stylesheet_link_tag

and leave the default settings on your webserver, the assets are typically cached pretty well.

回答4:

The cleaner way would be to write a Rack middleware, which changes the Cache-Control header based on some logic (for example, only for application/xml mime-type). Or, for an uglier, but still working approach, one could change the ActionDispatch::Response::DEFAULT_CACHE_CONTROL constant to \'no-cache\'. Of course, if the controller and/or action granularity is required, then it\'s better to do this in the controller.

回答5:

Point of note: You can\'t conditionally clear the cache (like if a before_filter only calls reset_cache if the user\'s already been there). You need to unconditionally clear the cache, because the browser won\'t make a new request just to see if this time, it needs to reload, even though it didn\'t need to last time.

Example:

before_filter :reset_cache, if: :user_completed_demographics?

won\'t work to prevent users from coming back after they\'ve been there, since the browser uses the original cache headers on the Back button.

before_filter :reset_cache

will work, however (after refreshing the page and clearing the cache from before you added this, obviously), since, on the first request, the browser will get the no-cache, no-store, ... and apply it to future page loads.