On Mon, Oct 30, 2017 at 3:23 PM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Mon, Oct 30, 2017 at 11:12 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> > wrote: >> On 2017-10-30 11:07, Jeroen Demeyer wrote: >>> >>> I just tried with my phone and the problem also occurs there! What is >>> wrong with me if I'm the only person having this problem? >> >> >> OK, the common source of problems might be my university network. I disabled >> wifi on my phone and now it seems to work... >> >> Still, the question remains: what could my network be doing which breaks >> logins to Trac? > > Hard to imagine--maybe the university network has a proxy that is > stripping/corrupting some request and/or response headers? > > Is there an easy way you could capture and send me a capture of those > headers when you login e.g. using your browser's developer tools? > Might be helpful to look at for comparison's sake.
On second thought, one thing I just remembered: We have a setting enabled that ties Trac cookies to an IP address: If you connect with an existing cookie from a different IP address from when it was created, that cookie is treated as invalid and should be forced to expire, thus forcing you to re-login. Is it possible you're using Tor or some other sort VPN that uses a different IP address on each request? This has been a problem for some people before. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
