mirrors/django
mirrors/django
0
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-11-30 15:10:46 +01:00
Code Issues Releases Wiki Activity

Fixed #5550: Documented the context used by the default view for 404 and 500 errors.

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@6808 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2007-12-01 20:11:55 +00:00
parent b2dbbd5bbc
commit 7fbe014197
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/request_response.txt
View File

@ -555,10 +555,13 @@ Three things to note about 404 views:
* The 404 view is also called if Django doesn't find a match after checking * The 404 view is also called if Django doesn't find a match after checking
every regular expression in the URLconf. every regular expression in the URLconf.
* If you don't define your own 404 view -- and simply use the default, * If you don't define your own 404 view -- and simply use the
which is recommended -- you still have one obligation: To create a default, which is recommended -- you still have one obligation:
``404.html`` template in the root of your template directory. The default To create a ``404.html`` template in the root of your template
404 view will use that template for all 404 errors. directory. The default 404 view will use that template for all
404 errors. The default 404 view will pass one variable to the
template: ``request_path``, which is the URL which resulted in
the 404.
* If ``DEBUG`` is set to ``True`` (in your settings module) then your 404 * If ``DEBUG`` is set to ``True`` (in your settings module) then your 404
view will never be used, and the traceback will be displayed instead. view will never be used, and the traceback will be displayed instead.
@ -572,7 +575,8 @@ the view ``django.views.defaults.server_error``, which loads and renders the
template ``500.html``. template ``500.html``.
This means you need to define a ``500.html`` template in your root template This means you need to define a ``500.html`` template in your root template
directory. This template will be used for all server errors. directory. This template will be used for all server errors. The
default 500 view passes no variables to this template.
This ``server_error`` view should suffice for 99% of Web applications, but if This ``server_error`` view should suffice for 99% of Web applications, but if
you want to override the view, you can specify ``handler500`` in your you want to override the view, you can specify ``handler500`` in your