From 5ad144b29e161508faea55085dc1b4037150fc8b Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Sat, 26 Nov 2005 03:17:52 +0000 Subject: [PATCH] Added 'Error handling' section to docs/modpython.txt git-svn-id: http://code.djangoproject.com/svn/django/trunk@1437 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/modpython.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/modpython.txt b/docs/modpython.txt index c444a292ef..3444087785 100644 --- a/docs/modpython.txt +++ b/docs/modpython.txt @@ -176,3 +176,16 @@ Here are two recommended approaches: change. 2. Or, copy the admin media files so that they live within your document root. + +Error handling +============== + +When you use Apache/mod_python, errors will be caught by Django -- in other +words, they won't propogate to the Apache level and won't appear in the Apache +``error_log``. + +The exception for this is if something is really wonky in your Django setup. In +that case, you'll see an "Internal Server Error" page in your browser and the +full Python traceback in your Apache ``error_log`` file. The ``error_log`` +traceback is spread over multiple lines. (Yes, this is ugly and rather hard to +read, but it's how mod_python does things.)