在 2010年12月10日星期五UTC+8下午9时57分20秒,Tom Evans写道:
>
> On Fri, Dec 10, 2010 at 1:27 PM, Stodge >
> wrote:
> > I have SESSION_EXPIRE_AT_BROWSER_CLOSE set to True in my settings.
> > When the user visits my custom login page a new session is created for
> > them in the database. The expiry time is set t
Ok thanks. I'm trying to limit the number of concurrent users using
sessions.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
djan
AFAIK there is a known bug in FireFox preventing it from working correctly. Try
(nearly) any other browser.
"Stodge" schrieb:
>I have SESSION_EXPIRE_AT_BROWSER_CLOSE set to True in my settings.
>When the user visits my custom login page a new session is created for
>them in the database. The
On Fri, Dec 10, 2010 at 1:27 PM, Stodge wrote:
> I have SESSION_EXPIRE_AT_BROWSER_CLOSE set to True in my settings.
> When the user visits my custom login page a new session is created for
> them in the database. The expiry time is set to two weeks.
>
> If I then close the browser, the expiry hour
I have SESSION_EXPIRE_AT_BROWSER_CLOSE set to True in my settings.
When the user visits my custom login page a new session is created for
them in the database. The expiry time is set to two weeks.
If I then close the browser, the expiry hour/minute are adjusted but
it's still set to two weeks in t
5 matches
Mail list logo