> On Sunday, January 22, 2017 at 1:21:04 PM UTC+5, ADEWALE ADISA wrote:
>>
>> Good day;
>> Please i need help on the issues am facing on
>> SESSION_EXPIRE_AT_BROWSER_CLOSE django settings.py. In my setting file i
>> have:
>>
>> SESSION_EXPIRE_AT_BROW
Im facing the same problem, How did you solve this problem?
On Sunday, January 22, 2017 at 1:21:04 PM UTC+5, ADEWALE ADISA wrote:
>
> Good day;
> Please i need help on the issues am facing on
> SESSION_EXPIRE_AT_BROWSER_CLOSE django settings.py. In my setting fi
thanks again Mr James.
am able to solve the problem now by running the management command "python
manage.py clearsessions".
This pratically delete all the session stored on the django session
database.
so SESSION_EXPIRE_AT_BROWSER_CLOSE behave as it should now.
On Jan 22, 2017 9:41
after closing and re-opening the browser. In
some cases, this can interfere with the SESSION_EXPIRE_AT_BROWSER_CLOSE
setting and prevent sessions from expiring on browser close. Please be
aware of this while testing Django applications which have the
SESSION_EXPIRE_AT_BROWSER_CLOSE setting enabled
Make sure you're not looking at users who already had a session cookie set
before you changed the setting. Existing cookies might not get immediately
rewritten to have the shorter expiration.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
Good day;
Please i need help on the issues am facing on
SESSION_EXPIRE_AT_BROWSER_CLOSE django settings.py. In my setting file i
have:
SESSION_EXPIRE_AT_BROWSER_CLOSE = True
but unfortunately, whenever my users close there browsers and open it
again, they are login automatically, which shows
在 2010年12月10日星期五UTC+8下午9时57分20秒，Tom Evans写道：
>
> On Fri, Dec 10, 2010 at 1:27 PM, Stodge <sto...@gmail.com >
> 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 f
On Monday 31 January 2011 18:38:20 Tim Sawyer wrote:
> > You can't stop the user from closing the browser, or switching to another
> > tab, with JS. And you shouldn't try to stop them navigating away - this
> > sort of thing is only likely to annoy them intensely.
>
> Taking this to the extreme -
> You can't stop the user from closing the browser, or switching to another
> tab, with JS. And you shouldn't try to stop them navigating away - this
> sort of thing is only likely to annoy them intensely.
Taking this to the extreme - what do you want to happen if a person using
your site has a
On Monday, January 31, 2011 3:06:29 PM UTC, Ivan Uemlianin wrote:
>
> Dear Tom
>
> Thanks for your comment.
>
> My use case is a "presence"-type system. When a user logs out their
> status change is sent out to all other logged-in users (using comet).
> If they just close the browser this
ooglemail.com> wrote:
> On Mon, Jan 31, 2011 at 2:21 PM, Ivan Uemlianin <i...@llaisdy.com> wrote:
> > Dear All
>
> > Is the setting SESSION_EXPIRE_AT_BROWSER_CLOSE mis-named? As far as I
> > can tell the setting doesn't influence the session expiry at all
>
On Mon, Jan 31, 2011 at 2:21 PM, Ivan Uemlianin <i...@llaisdy.com> wrote:
> Dear All
>
> Is the setting SESSION_EXPIRE_AT_BROWSER_CLOSE mis-named? As far as I
> can tell the setting doesn't influence the session expiry at all
> (e.g., what happens to the django_session table
Dear All
Is the setting SESSION_EXPIRE_AT_BROWSER_CLOSE mis-named? As far as I
can tell the setting doesn't influence the session expiry at all
(e.g., what happens to the django_session table on the server). What
this setting seems to affect is the expiry of the *cookie* in the
browser.
I'm
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
AFAIK there is a known bug in FireFox preventing it from working correctly. Try
(nearly) any other browser.
"Stodge" <sto...@gmail.com> schrieb:
>I have SESSION_EXPIRE_AT_BROWSER_CLOSE set to True in my settings.
>When the user visits my custom login page a new sessio
On Fri, Dec 10, 2010 at 1:27 PM, Stodge <sto...@gmail.com> 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.
>
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
5, 3:58 pm, pr <crico...@gmail.com> wrote:
>
> > Hello,
>
> > When I set SESSION_EXPIRE_AT_BROWSER_CLOSE to True, Django
> > automatically remove not only my session cookie (sessionid) but also
> > any others cookies creating by using response.set_cookie('myname',
&
you didn't specify max_age in response.set_cookie('myname', data),
which assumes None by default. Therefore that cookie expires when
browsers closes.
On Jun 25, 3:58 pm, pr <crico...@gmail.com> wrote:
> Hello,
>
> When I set SESSION_EXPIRE_AT_BROWSER_CLOSE to True, Django
> au
Hello,
When I set SESSION_EXPIRE_AT_BROWSER_CLOSE to True, Django
automatically remove not only my session cookie (sessionid) but also
any others cookies creating by using response.set_cookie('myname',
data). Why? I want to keep all cookies without session cookie.
Thank You
;
>
> which in practice means expire the session or not at the end of the session
>
> it looks like django's auth uses a sitewide setting
> SESSION_EXPIRE_AT_BROWSER_CLOSE
>
> does anybody know the best way to approach this ? is it the
> SessionMiddleware that should
you would end up needing a huge session store.
>
> it looks like django's auth uses a sitewide setting
> SESSION_EXPIRE_AT_BROWSER_CLOSE
>
> does anybody know the best way to approach this ? is it the
> SessionMiddleware that should be replaced ?
>
What you need is to send
I'm trying to implement the standard option "remember me on this computer"
which in practice means expire the session or not at the end of the session
it looks like django's auth uses a sitewide setting
SESSION_EXPIRE_AT_BROWSER_CLOSE
does anybody know the best way t
23 matches
Mail list logo
