Anyone have an idea what that means? This is appearing in my web app’s apache log and only to a user who is complaining that the web app kicks her out after about 2 minutes. I do have a session time out, but it is set to 10 minutes and works great for everyone else. This person can’t stay in the system for more than 2 minutes before the session is terminated (it seems that is what is happening, they defiantly get kicked out).
According to http://httpd.apache.org/docs/2.0/mod/core.html#timeout it means your app did not send or receive anything for a while, so you ran into Apache timeout. Maybe the user has set some block on ping or something that prevents a normal dialog between your app and its client ?
https://duckduckgo.com/?q=(70007)The+timeout+specified+has+expired shows a lot of discussions about that error message, seemingly often related to proxy problems.
I’ve seen this error with overly aggressive caching proxies. They see a request that they’ve seen before and just return return the cached response instead of forwarding it along to your app.
Is there a way to get around this with a Xojo web app? I’d assume not. The client is complaining that the old portal worked fine but the new does not. The old was written in Ruby on Rails, so a totally different architecture.
From what Greg said, I would tend to believe that the solution might be to regularly push new data to force the proxy to respond instead of simply serving the cache. Maybe by sending random named cookies and fetching them, then removing them ? From the Apache page, default timeout is 300 seconds. So you may try to set a timer to send something and request a response within that time frame.
Or maybe create a small animation, say with the current time on your page, that will force the proxy to let that pass from the server and satisfy Apache.