arzumy md short notes on small discoveries

Shared Session Cookies Gotchas

28 June 2011

Originally posted in Ruby on Rails - Malaysia (English) group.

Today I made a mistake. I pushed a line of code that effectively made the users can neither login nor logout. So I thought I’d shared the problem and solution with you guys


We want the session cookie to be shared within the subdomain. For example, could access session cookie from This allows seamless integration between multiple apps.


It’s easy to achieve that. You’ll just have to modify config/initializers/session_store.rb and add :domain option. Like so,

  MyApp::Application.config.session_store :cookie_store, :key => '_my_app_session', :domain => ""

That works, but it’s not so cool since you’ll have to hardcode domain name. Better solution would be to use :all value

  MyApp::Application.config.session_store :cookie_store, :key => '_my_app_session', :domain => :all

That will make session cookie’s host to be or if your domain is, it’ll be Cookie’s host will follow what ever you current domain.


They are two major problems when you deploy the code. First, current users now locked to their current session state. If they are logged in, they can’t logout and vice versa. This happens because we now have two session cookies with same name _my_app_session but with a different host. And when you have that situation, cookie with matching host will take precedence. Hence, we are reading the old cookie (the one with host which is wrong, so our session is messed up.

The user could fix this by clearing up the browser’s cookies. But that’s totally uncool. Also, this won’t affect the new user, so that, on the other hand, is cool.

The second problem is when working on the development environment, visiting http://localhost:3000 won’t work. Because we are expecting the cookie host to be .localhost but it’s always saved as localhost. It will always be invalid.


The solution is obvious, you just need to delete the old cookie and just read the new one. But somehow the implementation wasn’t that obvious to me at first. My first option was to add a line of code that will delete the old cookie. It works, but it’s not good because it’ll be a stale code after a while. That line will never be used once all old cookies delete, and never used on for users.

I’ve searched high and low for a better solution when it suddenly hits me. I don’t need to delete the old cookie, I just need to make sure the app won’t read it. Just invalidate the old cookie. Since I have a conflicted name, why don’t just change the name? So I did, and it works like a charm. My new session_store.rb looks like this:

  MyApp::Application.config.session_store :cookie_store, :key => '_new_my_app_session', :domain => :all

For second problem, a quick workaround is to not use localhost. Use alias like app.local, etc. Or just make sure shared domain not used in development mode, like so:

  MyApp::Application.config.session_store :cookie_store, :key => '_new_my_app_session', :domain => Rails.env.development? ? nil : :all

That’s about it. Now the app runs smoothly for old and new users.


arzumy md, CTO at Fave and BillPlz.