On Tue, 2009-03-10 at 18:52 -0700, Ryan wrote: > Yeah, it's definitely being set, and I've put nothing in the session. > As it turns out, just accessing a session value (@user_id = session > [:user_id]) is enough to make Rails write the session cookie. This > seems like a bug.
To me, also. > I worked around this by calling session.include? first, but I > shouldn't have to hit the hash twice just to avoid writing the session > cookie. Testing for an object's existence should not cause it to come into being. Kinda pees on the whole REST parade. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
