Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fix cookie serializer docs

The option actually needs to be set on action_dispatch. [ci skip]

Conflicts:
	guides/source/upgrading_ruby_on_rails.md
  • Loading branch information...
commit a16824aa00a9d4cdc6b05dac5bf18550f4f4d610 1 parent 318a20c
@carlosantoniodasilva carlosantoniodasilva authored rafaelfranca committed
Showing with 3 additions and 3 deletions.
  1. +3 −3 guides/source/upgrading_ruby_on_rails.md
View
6 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.
Please sign in to comment.
Something went wrong with that request. Please try again.