Dear Community
When a user clicks the logout button they are not being returned to the home page. Instead the browser gets stuck in an unending loop calling the home page but never seeming to get it or display it. This kills the browser and also Apache which runs out of resources. My environment is:
OS: CentOS Linux release 7.0.1406 (Core)
Apache Version: Apache/2.4.6 (CentOS)
Xerte Toolkit Version: 2.1 (git git-103-gebc6f34)
Whilst stuck in the loop the Apache access_log displays the following approximately three times per second:
***.***.18.250 - - [28/Apr/2015:10:36:27 +0100] "GET /xertetoolkits/ HTTP/1.1" 200 2732 "
myserver.swan.ac.uk/xertetoolkits/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0"
***.***.18.250 - - [28/Apr/2015:10:36:27 +0100] "GET /xertetoolkits/ HTTP/1.1" 200 2732 "
myserver.swan.ac.uk/xertetoolkits/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0"
***.***.18.250 - - [28/Apr/2015:10:36:27 +0100] "GET /xertetoolkits/ HTTP/1.1" 200 2732 "
myserver.swan.ac.uk/xertetoolkits/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0"
***.***.18.250 - - [28/Apr/2015:10:36:27 +0100] "GET /xertetoolkits/ HTTP/1.1" 200 2732 "
myserver.swan.ac.uk/xertetoolkits/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0"
It looks like the Browser although successfully accessing the page (200) never actually gets it.
If I kill the browser session and then goto
myserver.swan.ac.uk/xertetoolkits/ the page loads without any problem.
My best guess is that a PHP script that gets triggered by the clicking the logout button is causing some kind of internal loop - possibly related to killing off a session...
After a quick look around the codebase (gulp!) I'm unable to see any reason for the oddity and am stumped. Can anyone help?
thanks in advance
