Browse files

Fixed #6278 -- Documented that the 404 template is passed a RequestCo…

…ntext and the 500 handler is not. Thanks, Rob Hudson.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 5f47776 commit 66747182131de06b787d19c164f30fcfc0c625ce @malcolmt malcolmt committed Feb 4, 2008
Showing with 7 additions and 2 deletions.
  1. +7 −2 docs/request_response.txt
@@ -575,6 +575,10 @@ Three things to note about 404 views:
to the template: ``request_path``, which is the URL that resulted
in the 404.
+ * The 404 view is passed a ``RequestContext`` and will have access to
+ variables supplied by your ``TEMPLATE_CONTEXT_PROCESSORS`` (e.g.
+ ``MEDIA_URL``).
* 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.
@@ -587,8 +591,9 @@ the view ``django.views.defaults.server_error``, which loads and renders the
template ``500.html``.
This means you need to define a ``500.html`` template in your root template
-directory. This template will be used for all server errors. The
-default 500 view passes no variables to this template.
+directory. This template will be used for all server errors. The default 500
+view passes no variables to this template and is rendered with an empty
+``Context`` to lessen the chance of additional errors.
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

0 comments on commit 6674718

Please sign in to comment.