On Mar 11, 1:52 am, Ryan <[email protected]> wrote:
> On Mar 10, 6:25 pm, Frederick Cheung <[email protected]>
> wrote:
>
> > Are you sure it's actually being set? rails 2.3 is only supposed to
> > set the session cookie if you've actually put something in the
> > session.
>
> 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.
>
> 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.
>
> Seem like bug to you?
>
If previously you had session :off, why are you accessing the session
at all ?
I don't think rails is trying to be too clever - any use of session
makes rails consider the session to be used (and so in need of
updates)
Fred
> Ryan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
