On 2 Mar 2011, at 18:54, Robert Calco <[email protected]> wrote:
> Anyone: > > > My problem is that when I authenticate the user in the interim action (the > one that ordinarily just redirects to /session/new) and attempt to take them > to the home page as freshly logged in users, they are mysteriously no longer > logged in, and it basically takes them to /session/new. Logging confirms that > they are logged_in? in this process, but once the redirect happens to the > subdomain, apparently they are not. This, even if I copy the very code in the > #create action that works fine when called from /session/new into a method > that I call from the interim action handler (SessionsController#user_login). > > I've tried all kinds of different ways to simulate a post from /session/new > to /session in that action handler but no luck. I must be missing some piece > of information that would lead to my "Well, duh" moment but it is eluding me > right now. Is there something in the session object I can manipulate? It's > using cookie storage. FYI, this is Rails 2.3.2 (yes, I know about the > security problem, will apply the patch as soon as I'm done with this code > update). I'd check the domain that being set on the session cookie (assuming logged-in-ness is stored in the session. If stored in a separate cookie then check that cookie Fred > > Thanks in advance, > > Bob > -- > 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. -- 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.
