#9430 closed (fixed)
Writing Views makes reference to previously mentioned issue but doesn't say where
Reported by: | Chris Lyon | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.0 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
http://docs.djangoproject.com/en/dev/topics/http/views/
to quote:
Returning HTTP error codes in Django is easy. We've already mentioned the HttpResponseNotFound, HttpResponseForbidden, HttpResponseServerError, etc., subclasses; just return an instance of one of those subclasses instead of a normal HttpResponse in order to signify an error. For example:
It says we've already mentioned but it would be useful if their were a pointer to where these errors are first mentioned. I came at this from a methodical reading of the view documentation and felt that their should have been some indication as to where these objects were first introduced.
Change History (2)
comment:1 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
(In [9266]) Fixed #9430 -- Fixed documentation references to the HttpResponse classes for
returning HTTP status codes other than 200.