On 2017-10-30 16:51, Erik Bray wrote:
Thanks to some request/response dumps Jeroen sent me, I think I can
take a guess at the problem.  His university has set up a forward
proxy to cache static HTTP resources, and so while his /login request
comes from his machine, or whatever NAT router it's behind, requests
for static resources on the site come from the proxy, which is
forwarding headers but is not at the same IP address.  So the check_ip
setting in the Trac config fails and invalidates his trac_auth cookie.

Thanks for the analysis and fix!

--
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.

Reply via email to