Its still the same issue, even when you glimpse at what is really going on here you figure out in the end that the idle timer is set at 1000ms on the server side but, the way the client login is managed is through a device that is a standalone capture port set to intercept the attempts of hackers. In other words, there is a box in front of the server that is handling logins that transports users to the server rather than an open face of the server being made publicly available. Alright so the idle timer is not set on the server but on the login pre-cursory device. At this point there is pretty much nothing you can do on a browser to avert this.