TIL Rails: Cache Control in Rails #8
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Whenever we load a page in browser, it will stores a cached version of
the page.
So if users press the back buttons, the browser will simply load the
cache version of the page.
This can be an issues when there sensitive information involve.
We can simply set the header `Cache-Control` in our
`application_controller.rb`
```ruby
before_filter :set_as_private
protected
def set_as_private
response.headers['Cache-Control'] = 'no-cache, no-store'
end
```
In the case where you only need it in specific page, just use the
`before_filter` in respective controller.
|
@jamesfwz and @stevenyap Kindly help me with my pull request. Thank you. |
stevenyap
added a commit
that referenced
this pull request
Nov 17, 2015
TIL Rails: Cache Control in Rails
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whenever we load a page in browser, it will stores a cached version of
the page.
So if users press the back buttons, the browser will simply load the
cache version of the page.
This can be an issues when there sensitive information involve.
We can simply set the header
Cache-Controlin ourapplication_controller.rbIn the case where you only need it in specific page, just use the
before_filterin respective controller.