diff options
author | Santiago Pastorino <santiago@wyeworks.com> | 2013-04-01 10:45:55 -0700 |
---|---|---|
committer | Santiago Pastorino <santiago@wyeworks.com> | 2013-04-01 10:45:55 -0700 |
commit | e456ad514aca81cbcb67ea9d919730ac00724a38 (patch) | |
tree | 96b66afdda7404d425e7c9acd48b7027753d19a2 /guides/source/upgrading_ruby_on_rails.md | |
parent | 456bd7bfade62c6057649fb57a254fa931276470 (diff) | |
parent | ca58bf1543f515e560bdcdb0b7dc4c957e893f72 (diff) | |
download | rails-e456ad514aca81cbcb67ea9d919730ac00724a38.tar.gz rails-e456ad514aca81cbcb67ea9d919730ac00724a38.tar.bz2 rails-e456ad514aca81cbcb67ea9d919730ac00724a38.zip |
Merge pull request #10031 from trevorturk/cookie-store-auto-upgrade-docs
Improve documentation around the cookie store auto-upgrade to encryption
Diffstat (limited to 'guides/source/upgrading_ruby_on_rails.md')
-rw-r--r-- | guides/source/upgrading_ruby_on_rails.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md index 83134fcf87..a8182617f3 100644 --- a/guides/source/upgrading_ruby_on_rails.md +++ b/guides/source/upgrading_ruby_on_rails.md @@ -94,7 +94,7 @@ Please note that you should wait to set `secret_key_base` until you have 100% of If you are relying on the ability for external applications or Javascript to be able to read your Rails app's signed session cookies (or signed cookies in general) you should not set `secret_key_base` until you have decoupled these concerns. -* Rails 4.0 encrypts the contents of cookie-based sessions if `secret_key_base` has been set. Rails 3.x signed, but did not encrypt, the contents of cookie-based session. Signed cookies are "secure" in that they are verified to have been generated by your app and are tamper-proof. However, the contents can be viewed by end users, and encrypting the contents eliminates this caveat/concern. +* Rails 4.0 encrypts the contents of cookie-based sessions if `secret_key_base` has been set. Rails 3.x signed, but did not encrypt, the contents of cookie-based session. Signed cookies are "secure" in that they are verified to have been generated by your app and are tamper-proof. However, the contents can be viewed by end users, and encrypting the contents eliminates this caveat/concern without a significant performance penalty. As described above, existing signed cookies generated with Rails 3.x will be transparently upgraded if you leave your existing `secret_token` in place and add the new `secret_key_base`. @@ -106,6 +106,8 @@ As described above, existing signed cookies generated with Rails 3.x will be tra The same caveats apply here, too. You should wait to set `secret_key_base` until you have 100% of your userbase on Rails 4.x and are reasonably sure you will not need to rollback to Rails 3.x. You should also take care to make sure you are not relying on the ability to decode signed cookies generated by your app in external applications or Javascript before upgrading. +Please read [Pull Request #9978](https://github.com/rails/rails/pull/9978) for details on the move to encrypted session cookies. + * Rails 4.0 removed the `ActionController::Base.asset_path` option. Use the assets pipeline feature. * Rails 4.0 has deprecated `ActionController::Base.page_cache_extension` option. Use `ActionController::Base.default_static_extension` instead. |