On Sat, 2007-03-17 at 11:21 -0700, cwurld wrote:
> Does anyone know how the SESSION_EXPIRE_AT_BROWSER_CLOSE works? In
> other words, how does the Django session know the browser closed? It
> seems like this mechanism could be used to accomplish the above.
It's an HTTP cookie feature: if you don't
Does anyone know how the SESSION_EXPIRE_AT_BROWSER_CLOSE works? In
other words, how does the Django session know the browser closed? It
seems like this mechanism could be used to accomplish the above.
Chuck
--~--~-~--~~~---~--~~
You received this message because
I did it using PHP. It can be circumvented but it's not something
the average user would do. Everytime an user logins, the session id is
stored on a table, with the time and the user id. On every request by
every logged in user, I put every previous session ids from the user
id on an array, rem
> I would like to find a way to prevent users from simultaniously
> logging in from different computers but using the same username and
> password.
How do you define "different computers"?
A remote IP address, possibly cookies, and possibly JavaScript
are about all you have to work with to dete
The quick answer would be to check through
the session data for a matching user id, but
there's one possible wrinkle: How do you
know when a user has logged off?
In my case (not yet implemented), I'll have
a timeout, but that still doesn't address
the issue of a user losing a connection and
atte
Hi,
In order for users to use my Django site they must login. I am using
the standard auth app. I set the session to expire when the browser is
closed or when the user clicks a log out button.
I would like to find a way to prevent users from simultaniously
logging in from different computers but
6 matches
Mail list logo
