diff options
| author | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2014-04-02 13:19:13 -0300 |
|---|---|---|
| committer | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2014-04-02 13:19:13 -0300 |
| commit | 5aa4157ae44112f61ef923cab33fa1e0aa381e41 (patch) | |
| tree | cf9e8279a17cca3730565b57d2a1dfdfd3bbb1e2 | |
| parent | 654dd04af61727e94b293b6713d8775b8d8ad630 (diff) | |
| download | rails-5aa4157ae44112f61ef923cab33fa1e0aa381e41.tar.gz rails-5aa4157ae44112f61ef923cab33fa1e0aa381e41.tar.bz2 rails-5aa4157ae44112f61ef923cab33fa1e0aa381e41.zip | |
Fix cookie serializer docs
The option actually needs to be set on action_dispatch. [ci skip]
| -rw-r--r-- | guides/source/upgrading_ruby_on_rails.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md index 0045206c76..88c9981dbb 100644 --- a/guides/source/upgrading_ruby_on_rails.md +++ b/guides/source/upgrading_ruby_on_rails.md @@ -104,9 +104,9 @@ Applications created before Rails 4.1 uses `Marshal` to serialize cookie values the signed and encrypted cookie jars. If you want to use the new `JSON`-based format in your application, you can add an initializer file with the following content: - ```ruby - Rails.application.config.cookies_serializer = :hybrid - ``` +```ruby +Rails.application.config.action_dispatch.cookies_serializer = :hybrid +``` This would transparently migrate your existing `Marshal`-serialized cookies into the new `JSON`-based format. |