On Mon, Jul 13, 2009 at 7:27 AM, Vitaly <hash...@gmail.com> wrote: > > Hi > > I have some problem with customizing error pages when application does > not work at all. One of things is stopping database on production > server and user should see normal description of problem. But instead > of this user see 'Unhandled exception' > > Does there method to avoid that and get flup know that django returns > 500 error. On production we're using nginx with proxying request to > django server. > > Thanks > > > The reason for this is that you have some queries being executed during middleware and Django currently doesn't catch exceptions that are thrown from middleware. This is the subject of ticket http://code.djangoproject.com/ticket/6094
Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Voltaire "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
