innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #14713 -- documented that resolve can raise Http404. Thanks to Adam for the patch. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14603 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Alex Gaynor 2010-11-17 20:03:15 +00:00
parent fc47f8c65a
commit 204253ed40
2 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/topics/http/urls.txt
View File

@ -837,6 +837,9 @@ worry about the ``urlconf`` parameter. The function returns a
:class:`django.core.urlresolvers.ResolverMatch` object that allows you :class:`django.core.urlresolvers.ResolverMatch` object that allows you
to access various meta-data about the resolved URL. to access various meta-data about the resolved URL.
If the URL does not resolve, the function raises an
:class:`~django.http.Http404` exception.
.. class:: ResolverMatch() .. class:: ResolverMatch()
.. attribute:: ResolverMatch.func .. attribute:: ResolverMatch.func

2
docs/topics/http/views.txt
View File

@ -95,6 +95,8 @@ to handle those errors.
The Http404 exception The Http404 exception
--------------------- ---------------------
.. class:: django.http.Http404()
When you return an error such as ``HttpResponseNotFound``, you're responsible When you return an error such as ``HttpResponseNotFound``, you're responsible
for defining the HTML of the resulting error page:: for defining the HTML of the resulting error page::