Hi all, Thanks for the help, The problem now solved... it's a silly mistake we randomly generated secret key of AuthTktAuthenticationPolicy, thus causing the problem after we fix the key, everything working perfectly...
Thanks, thanks all Regards, Desson On Sunday, January 10, 2016 at 4:58:29 AM UTC+8, Mike Orr wrote: > > On Thu, Jan 7, 2016 at 7:29 PM, Desson Ariawan <teod...@gmail.com > <javascript:>> wrote: > > Hi Luis, > > > > Thanks for your insight. But it shouldn't be the case. I test this in > our > > staging environment, which only referred by IP, not by any-name. And the > > scenario also failed for ext:database > > During 'tracing' I found that pyramid's request.unauthenticated_userid > > and/or request.authenticated_userid may/may not return expected 'stored' > > value... > > Cookies sometimes work improperly in IP-based testing due to edge > cases where the browser thinks it's the same or a different site. This > has most often occurred to me when I have two sites running > simultaneously on different ports; I think the browser considers them > the same site, which I wouldn't. However, I do have two sites which > are meant to share cookies (one is a mobile site for the other), and I > think it works when you switch between them (i.e., your last search is > still remembered). > > Also, forgetting the user unexpectedly would suggest a cookie-based > problem. If you can access the site through 'localhost' or if the IP > has a network-assigned domain, it may behave differently under those, > and that may give a clue to the problem. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
