hi
what i can understand now is while you are running your application on a
browser based VPN the problem is the browser accumulates a session id after
you logout first time because of session id and when you login back again
there is a session conflict and the user is automaticlly logged
I don't recall any similar reports. Anyway, "is it a bug?" questions go to
django-users. You'll need to include steps to reproduce the issue in order
to get help.
On Wednesday, May 4, 2016 at 7:29:52 AM UTC-4, Samarjeet Singh wrote:
>
> the problem is on the flush function of django 1.8 and
i think this is a development issue because of request.session.flush if i
logout all the session detail is deleted and not modified because of which
next time when we login there is a session conflict so i dont know if it
ths problem is with everyone or only i am facing it .
Please help!!
On
the problem is on the flush function of django 1.8 and because of which the
session is deleted instead of modifying and then a new session is created
at logout and which gets conflicted with the new user session so that is
why i am not able to log in .so is this problem with me only or others
Hi,
this mailing list is about the development of Django itself. Please direct
usage questions to the django-users mailing list.
Cheers,
Florian
On Tuesday, May 3, 2016 at 12:06:44 PM UTC+2, Samarjeet Singh wrote:
>
> The problem i am facing is :
> 1.login to the app every thing is fine
>
The problem i am facing is :
1.login to the app every thing is fine
2.logout
3.login back again (then if i click on any tab it redirects me to the login
page back again )
any idea what can be the problem ???
PS:one more thing previously when the user does a login the number of key
was same in
