Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not working for rails 3.2.x #1

Closed
equivalent opened this issue Nov 18, 2014 · 3 comments
Closed

not working for rails 3.2.x #1

equivalent opened this issue Nov 18, 2014 · 3 comments

Comments

@equivalent
Copy link
Owner

not working for rails 3.2.20 more details here http://stackoverflow.com/questions/26994714/how-to-force-cache-control-to-no-store-in-rails-3-2-20

@equivalent
Copy link
Owner Author

as discussed here http://stackoverflow.com/questions/26994714/how-to-force-cache-control-to-no-store-in-rails-3-2-20/27498300#27498300

With Rails 3.2 the gem no_cache_control only works when the rails app is booted in production mode.

so this should work when running rails app on production, staging, ..

RAILS_ENV=production rails s 

thank you Barlow

@equivalent
Copy link
Owner Author

I've tested the no_cache_control gem on one other project with rails 4.1 and it works on Development

@equivalent
Copy link
Owner Author

in rails 3.2.x I was trying to change the config/environments/development.rb as close to production env as I could but nothing. It seems this is something in the core of Rails controllers

so only remaining solution is to run rails on production

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant