Sorry for the confusion. Web2py stores session data, by default, on disk, and that sounds like what you're doing.
There is a way to make it store session data in a separate database, by calling session.connect(...). On Feb 9, 2:31 pm, Johann Spies <[email protected]> wrote: > On 9 February 2010 21:14, Dmitri Zagidulin <[email protected]> wrote: > > > Several questions. Are you storing sessions on disk, or in a database? > > I do not clearly understand what you mean by "storing sessions". I > use sqlite as database. > > > > > What's the decorator you're using, to require login? (is it > > @auth.requires_login()?) > > Yes. > > > Is the 'user' function exposed, for those controllers? > > Yes and while checking I found that there were two identical 'user' > functions in the controller. I have commented one out now but I still > have to log in twice. > > > Do you have any custom routes.py or apache mod_rewrite routing that > > might be interfering? > > No. The system is running behind apache + wsgi using https. > > No mod_rewrite or custom routes.py. > > Regards > Johann -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
