Rearding session_key validation
Right now what django is doing is :- 1. It checks the session id is correct or not by checking the user associated with the session id 2. If the session id is not present it send the user as anonomous and because of which it redirects one to the login page . 3. But my concern is that if i want to log this event in the audit log of my application using django to get the false session id request.Is it possible to write a middleware for this?? regards samarjeet singh -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/132029df-d095-47e9-801f-4b8283010f37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Rearding session_key validation
Right now what django is doing is :- 1. It checks the session id is correct or not by checking the user associated with the session id 2. If the session id is not present it send the user as anonomous and because of which it redirects one to the login page . 3. But my concern is that if i want to log this event in the audit log of my application using django to get the false session id request.Is it possible to write a middleware for this?? regards samarjeet singh -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/12c53b2c-dac6-4868-a596-023826455d04%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: upgrade from 1.4 to 1.8
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 out!! On Wednesday, May 4, 2016 at 8:54:25 PM UTC+5:30, Tim Graham wrote: > > 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 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 also >> >> >> On Tuesday, May 3, 2016 at 6:19:57 PM UTC+5:30, Florian Apolloner wrote: >>> >>> 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 >>>> 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 the session table(the session key was modified) but now in >>>> 1.8 the number of session key entry increases by two or more. >>>> >>> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8d166f5e-e229-4fc6-80f3-f45b77f10290%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: upgrade from 1.4 to 1.8
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 Tuesday, May 3, 2016 at 3:36:44 PM UTC+5:30, Samarjeet Singh wrote: > > 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 the session table(the session key was modified) but now in 1.8 > the number of session key entry increases by two or more. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a83eb091-1f8c-4be2-a6b7-3f58d99e189d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: upgrade from 1.4 to 1.8
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 also On Tuesday, May 3, 2016 at 6:19:57 PM UTC+5:30, Florian Apolloner wrote: > > 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 >> 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 the session table(the session key was modified) but now in 1.8 >> the number of session key entry increases by two or more. >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7f37a97d-d9d9-49ca-a51f-6a84f34fc556%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
upgrade from 1.4 to 1.8
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 the session table(the session key was modified) but now in 1.8 the number of session key entry increases by two or more. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a7c92983-7955-4fbf-8754-bd6522748c7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
