On Jan 7, 8:53 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > I'd still recommend you upgrade as the changes related to daemon mode > also touched common code used by embedded mode.
I'll go ahead and do that. > BTW, if the user is seeing the error it implies that you must be > displaying tracebacks through web.py somehow, as tracebacks don't get > displayed back to a client by mod_wsgi. Thus no way they could see the > error normally. I misspoke. The user didn't see it, the variables in the traceback showed that it was a real user who hit it. I contacted him and he was saving a very large form, and admitted he had clicked refresh a few times. I guess that would have broken the connection and caused this? > > The only other option would be that you are using some Apache input > filter which is giving problems. What version of Apache are you using? > What Apache input filters do you have configured? I don't think I have any filters set up. I'm on Apache/2.2.3 > Even if the problem was caused by browser or an intermediate proxy > closing incoming client side of socket connection, would be odd that > it isn't closing the outgoing side as well, although depends on the > proxy. > > Anyway, my recommendation would be making sure you are using latest > versions of mod_wsgi (1.3) and of Apache, or at least latest patch > revision for version of Apache being used. If you aren't using recent > versions, impossible to be sure that problem, if one does exist, isn't > already fixed. How do I make sure I have the latest version of Apache? Should my package manager handle that? Thanks again Greg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
