Ticket #5550: doc404.diff

docs/request_response.txt

@@ -558 +558 @@
     * If you don't define your own 404 view -- and simply use the default,
       which is recommended -- you still have one obligation: To create a
       ``404.html`` template in the root of your template directory. The default
-      404 view will use that template for all 404 errors.
+      404 view will use that template for all 404 errors. The context of that
+      template will contain the path of the requested URL (e.g.,
+      ``'/app/pages/bad_page/'``) in the variable ``request_path``.
 
     * 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.
@@ -572 +574 @@
 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.
+directory. This template will be used for all server errors. No specific
+information about the error will be added to the context of that template.
 
 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

docs/tutorial03.txt

@@ -341 +341 @@
     * If you don't define your own 404 view -- and simply use the default,
       which is recommended -- you still have one obligation: To create a
       ``404.html`` template in the root of your template directory. The default
-      404 view will use that template for all 404 errors.
+      404 view will use that template for all 404 errors.The context of that
+      template will contain the path of the requested URL (e.g.,
+      ``'/app/pages/bad_page/'``) in the variable ``request_path``.
     * 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.