Post by aju on Nov 2, 2018 13:27:23 GMT
My chrome reloader extension sets and un-sets timers and seems to just do a window.location.reload() command when the timer has counted down to zero. At least that's all it seems to do as far as I can tell. I just amended one of the auto refresh extensions on Chromes apps screens.
I have noticed that sometimes when I return the system has logged out - the timers are still going but just stuck at a relevant logged out point and reloading that. Most of the time it seems to have failed is due to Zopa making on the fly changes and perhaps kicking me out to make them.
When I was told the timers were reduced to 4 minute last week I was surprised to see the Zopa system still telling me it was 15 mins on the logout screens.
As I said my extension I grabbed was on Chromes apps, I just checked it wasn't doing anything I wasn't happy about by checking what code looked active. I then removed all the calls to google stuff - I find that people amend these things and then add their add calls etc I didn't want that - I then updated the name of the extension so I could tell it was mine and reloaded it back into my browser. Whilst its not easy to follow a lot of what's going on inside it really is just a min and secs count down before forcing a simple inscreen reload.
At this point it may be useful to say that Zopa's current tracking of where you are seems to be affected by the reloader in that it does seem to stop the logout sequencing correctly but as I don't really use zopa's links anymore i'm expecting a few oddities. For efficiency and to mostly reducing time wasting for slow load of screens I am not interested in I use my own links, these also upset Zopa's tracking as well. The thing is though I'm not convinced Zopa is using the right mechanisms for what they are trying to achieve but that's just my view.
The other thing is what is causing most of the logout oddities is probably the the passing of data bewteen the auth server and the secure2 server.
Edit: So the active timer cookie on my latest session suggests that the timer is set at 15:02 minutes
Created
: Friday, 2 November 2018 at 14:57:50
Expires
: Friday, 2 November 2018 at 15:12:52
This is 15 mins 2 secs, by my reckoning