We have been struggling to handle logout on browser or tab close.
We checked our apache ssl_log and found following. On actual logout: ============ 115.112.67.33 - - [31/Jan/2014:07:21:24 -0500] "POST /hitinsiderEHRWeb/rest/logout HTTP/1.1" 202 58 115.112.67.33 - - [31/Jan/2014:07:21:25 -0500] "GET /hitinsider_logout.php HTTP/1.1" 302 1863 115.112.67.33 - - [31/Jan/2014:07:21:27 -0500] "GET /simplesaml/www/module.php/saml/sp/saml2-logout.php/hitinsider-sp-hitinsider?SAMLResponse=fZLBbsIwDIZfpcq9TZOGskZQaRoXJHYZiMMuU0idUalNojode%2FyVMMQ2TZyi2P7%2B%2FLazQNV3Xm7cuxvDC6B3FiH57DuLMqaWZBysdApblFb1gDJouX183kie5dIPLjjtOvIDuU8oRBhC6yxJ1qsleWt4yQ2Icq6FyWemKoqZyk3ORKGh0MyYEnRRVWAYSfYw4EQuySQ04YgjrC0GZcMUmpA0Z2nBdoxLziQvX0myAgytVSFSxxA8Sko%2F2onpddZqNUCmXU%2Bx7X0HZ%2FP0dDrR3jVjB5k%2FehpjeDl52sUxxUSEU%2FTpt9rkx17nt3NTYywXB3VgJTSCz4vDAztoLnKhlDa6rJjhpqnycgbFnNSLs7yMDQ311Wbb%2BJtFKYT4azN6OpfRHoJqVFBnZwv6U2xx2e82qDDi79uTayDZq26E%2BxvDWC23o9aASGh9eeEmSv%2F7Q%2FUX&RelayState=_e6ae866769237f74c8f16d4a04dcd971e04af4db4e HTTP/1.1" 302 565 115.112.67.33 - - [31/Jan/2014:07:21:27 -0500] "GET /hitinsider.php HTTP/1.1" 302 1813 On tab close: ======== 115.112.67.33 - - [31/Jan/2014:07:20:23 -0500] "POST /hitinsiderEHRWeb/rest/logout HTTP/1.1" 202 58 115.112.67.33 - - [31/Jan/2014:07:20:24 -0500] "GET /hitinsider_logout.php?callback=undefined&_=1391170731453 HTTP/1.1" 302 1875 On browser: ======== 115.112.67.33 - - [31/Jan/2014:07:24:05 -0500] "POST /hitinsiderEHRWeb/rest/logout HTTP/1.1" 202 58 115.112.67.33 - - [31/Jan/2014:07:24:05 -0500] "GET /hitinsider_logout.php?callback=undefined&_=1391170952973 HTTP/1.1" 302 565 115.112.67.33 - - [31/Jan/2014:07:24:06 -0500] "GET /hitinsider.php HTTP/1.1" 302 1829 It seems to generate 302 message we have to open another empty window and from there we have to call hitinsider_logout.php to do further processing. Any suggestion on this topic?
