hi frederick yes im using cookistore.mayb i've expressed myself wrong. lets say im on my landing page, refresh and print out the sessiond: cd97142191ba68518a5f36d15d63299d
then i do a login plus store the session immedialty into the db and get redirected to the indexview which now shows: 1d1b8ccd73d99c218fc3e07fd19dc452 in the db i have: 472aa86f3bcb9a77b54889e94956b448 so something i dont really get here. i need a reference for a non-rails app...thats why the cookie and the overhead with addtionally storing it/ what im i not seing here? thx On Tue, Sep 13, 2011 at 1:02 PM, Frederick Cheung <[email protected]> wrote: > > > On Sep 13, 5:58 pm, tom <[email protected]> wrote: >> hi >> >> running a working rails3 + devise app. >> once i sign in, i store the session id in the db. then when i go back >> to the index view, the id is different. how can that be? >> im always using: > > What session store are you using? If you are using the cookie store > (this is the default) then this is normal - for this store the session > cookie isn't the id of a database row, memcache key etc, but the > actual contents of the session > > Fred > >> controller >> request.session_options[:id] >> >> view: >> <%= logger.info session.inspect %> >> <hr> >> <%= request.session_options[:id] %> >> <br> >> <%= session['session_id'] %> >> >> could some pls helpme? >> thx > > -- > 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.
