Re:Rails 3.2 RC1: Faster dev mode & routing, explain queries...
by gonepostal on Tuesday December 20, 2011 @12:50AM
(#3372456)
IMHO the better solution would not to store marshalled objects in the session cookie. Especially ones that you don't have direct control over. There can't be any reasonable regression-test or upgrade test that could test for this.
Re:Rails 3.2 RC1: Faster dev mode & routing, explain queries...
by speleding on Tuesday December 20, 2011 @04:07AM
(#3372810)
The Rails flash is actually stored as a marshaled object in the cookie, so this broke for everyone who happened to have something stored in the flash at the time of upgrade (which is a lot of people). It should have been caught before but it did get fixed in the latest release.
My favorite bug during the upgrade: Someone decided (long ago) it'd be a good idea to store a Marshalled object in the session-cookie. One class serialized therein disappeared in Rails 3.1. Result? Any and all requests with a session-cookie bomb out with an unmarshall error.
tldr: Make sure to rename your session cookie before rolling out the upgrade. This logs out all users but is still more desirable than the alternative...