On May 21, 10:16 am, Aljosa Mohorovic <[EMAIL PROTECTED]> wrote: > On May 20, 12:26 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > Generally you can ignore it, it usually indicates that the user > > pressed reload on a page or navigated off it before the browser could > > send through the whole request. > > > BTW, it is good idea to mention what hosting mechanism you are using > > when you get errors like this. I know this is generated by mod_python, > > but the majority wouldn't. > > thanks, i didn't know this is mod_python reported error and not on > django level, what kind of error would i receive in mod_wsgi or other > solutions?
In mod_wsgi you would probably see 'client connection closed'. At worst if something bad happened which more precise reason couldn't be determined then 'failed to write data'. The latter might occur though where an output filter in Apache implemented by some other Apache module screwed up. See: http://code.google.com/p/modwsgi/issues/detail?id=29 for an example error message and some discussion about whether or not there should be an ability to suppress the error message. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
