Thus said "Ashwin Hirschi" on Fri, 12 Dec 2014 00:29:57 +0100: > Unfortunately, it looks we've also run into strange crashes related to > (HTTP) redirection. Since many team members work from home, their IP > addresses jump around a lot. To help people find each other, we've set > up a simple redirection service.
I just committed a change that may address your issue. I haven't been able to reproduce the exact problem that you described (possibly because I don't have the redirect setup exactly like you did), but while investigating the code, I did find a problem which may be the cause. Basically, on a redirect Fossil did not completely reinitialize the address to which it was connecting. For a host where the redirect is simply to a new URI on the same host, this is not a problem, but for a redirection service as you have setup, I'm not sure how it ever worked because the address is going to be different for each redirect. If you get a chance, please try: http://www.fossil-scm.org/index.html/info/6e7cb7f27a190702593a2a54cbe5340453a13d74 Or if you don't yet have Fossil cloned: http://www.fossil-scm.org/index.html/zip/fossil-6e7cb7f27a.zip?uuid=6e7cb7f27a190702593a2a54cbe5340453a13d74 If this doesn't take care of the problem, more details about how the redirection is configured would be helpful, e.g. what kind of Redirect rules do you have in place? Apache or some other setup? Or even better would be some debug info from the core file if you can get it. Thanks, Andy -- TAI64 timestamp: 40000000548a90a7 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
