No the are still dealing with it. Typically when you "log in" to a web based service, it has no idea when you are "logging out" because there is no application to monitor.

The web server can only see new requests from the browser, which are only sent at specific times when hyperlinks are clicked, through javascript requests, etc.

For example if you log into Forms and then turn off your computer and visit the site the next day, you will still be logged in just as if you were sitting on the site the whole time.

Often web application will just log out out after a set period of time since the last request, for Forms it works a little odd and times you out after a set period of time from first login time, this means you can actually be logged out right immediately making a request.

Web Client has a period of time for log out as well, but it also has a triggered log out. I can reproduce the triggered log out by closing my browser. Somehow they found a way to detect that the browser was closed and immediately log out. I think this detection is what is going haywire and being triggered accidentally. I can't even begin to understand how it works though, since nothing on the workstation should be visible to the server.

In this case the client was using repository authentication and we edited the C:\Program Files\Laserfiche\Web Access\Web Files\web.config file and changed the default value of 30 for the timeout value to a higher value. That seems to have resolved the issue.