I'm not sure but I believe it has something to do with cookies only being sent as part of the header. I could be completely off base though.
-- Sent from my mobile device. Please excuse brevity and typos. On Jun 6, 2013, at 0:53, Mark Li <[email protected]> wrote: Does anyone know why the session.auth.remember and session.auth.expiration are only saved after a new page load? Currently, I am making an ajax call that sets session.auth.remember and session.auth.expiration (after auth.login_bare()). If I close the browser after the ajax call without a new page load, then the session.auth.remember is not saved and the user is not logged in. However, if I make the ajax call, then load a new page/refresh the page, and then close the browser, session.auth.remember is saved. Is there any reason why a page refresh/load does this, and why the ajax call alone will not save session.auth.remember and session.auth.expiration (and thus keep the user logged in)? -- --- You received this message because you are subscribed to a topic in the Google Groups "web2py-users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/web2py/HdoErSDw-z8/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
