Session Timeout Issues
It looks like nearly every PM or post I’ve attempted in the past few days has hit a session timeout (I’ll try to grab the specific error message). It…
It looks like nearly every PM or post I’ve attempted in the past few days has hit a session timeout (I’ll try to grab the specific error message). It actually just happened when submitting this one; the alert reads “Your request timed out. Please retry the request.” Heading back to the previous page usually lets me recover my text, though it seems some others have lost posts they were drafting. This might be browser-dependent since I’m on Chrome for OSX.
I know it’s not just my machine because my iPhone experienced it too while connected via AT&T 3G. That was through Mercury, which presumably runs the Safari engine.
Heads up to anyone writing a lengthy post: consider copying your text to the clipboard before hitting submit. -A
> Atone wrote: > It looks like nearly every PM or post I’ve attempted in the past few days has hit a session timeout (I’ll try to grab the specific error message). It actually just happened when submitting this one; the alert reads "Your request timed out. Please retry the request." Heading back to the previous page usually lets me recover my text, though it seems some others have lost posts they were drafting. This might be browser-dependent since I’m on Chrome for OSX. > > I know it’s not just my machine because my iPhone experienced it too while connected via AT&T 3G. That was through Mercury, which presumably runs the Safari engine. > > Heads up to anyone writing a lengthy post: consider copying your text to the clipboard before hitting submit. > > -A Yeah, I ran into something similar when drafting a reply that needed some thought and research. When I clicked 'submit', it redirected me to the login page. Even after logging back in and navigating up to the previous reply screen, my typed content was gone. It happened again today, but this time I had the sense to copy my text beforehand because I felt like I might be nearing the timeout limit...and indeed I did. I'm using FireFox 3.0.6 on Vista for this specific device. I *think* there's a 'keep alive' setting in the configuration somewhere...let me go check... Edit: Found it—the keep-alive option is already turned on in FF config. The board seems to be ignoring it or not recognizing it properly?
That’s a new one for me; I doubt it’s just a browser setting. Since I didn’t have to log in again, that might be why my text survived. -A
Yes, if you navigate away from your reply and then come back to it, the text usually remains cached...but if the system asks you to log in again and you do so, it vanishes. I haven't tested whether returning directly from that login prompt (without logging in yet) keeps the content. I adjusted the keep-alive timeout down from 300 to 100 just to observe the effect. Then I browsed a few other blogs for a while. When I returned, my session was still active, but since I don't know the exact time limit here, it's hard to say if that adjustment helped or if I simply hadn't been away long enough to get auto-logged out. I'll keep watching and see what happens—with me, it probably won’t be long before I spend another disproportionate amount of time drafting a reply.
It occurs with quick replies as well. -A ETA: Correction, it didn't happen on that specific quick reply; I must have been fast enough.
Since joining, this happens to me quite often. I always use 3G data, so I assumed it was related. Sometimes a Preview looks fine. Then, when I hit Submit, the message says the server connection was lost. I’ve learned to save my work before doing anything else because of these issues.
I've been trying to replicate the issue, but haven't encountered it on either my browser or phone. I also tested a few different browsers. Occasionally, however, the site is incredibly slow. I assume that happens when the PHPBB team performs some upgrades.
For what it's worth, this happened to me yesterday as well.
Tom; I had the issue at 9:50 PM. I'm noting the time because that's what they ask for. LRC has drilled it into me! Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. ________________________________________ Apache Server at the archived discussion Port 80 It worked fine after the third attempt.