So in that case it looks to me like web2py's timeout defaults to 3600 seconds (1 hour).
If a user had a form opened for over an hour and then attempted to submit the form, would that cause the form to be returned without errors just like the double form window would cause? If so, that's probably what was happening as that seems much more likely than having two form windows open. If that is the case, starting a JS timer on each page that alerted and redirected after an hour would solve this problem correct? On Sep 15, 2:14 pm, Anthony <[email protected]> wrote: > On Thursday, September 15, 2011 2:03:24 PM UTC-4, Lennon wrote: > > > In that case does anybody have any ideas about how to gracefully > > handle this Session problem without removing session from > > form.accepts? > > > Anthony suggested having a javascript pop-up when the session times > > out but don't web2py sessions not timeout while the browser remains > > open be default? > > If the browser is open but not sending any requests back to the server, the > server has no way of knowing it is still open, so the session can still time > out. > > Anthony
