Code

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#9430 closed (fixed)

Writing Views makes reference to previously mentioned issue but doesn't say where

Reported by: wyleu Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation:
Needs tests: Patch needs improvement:
Easy pickings: UI/UX:

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.

Attachments (0)

Change History (2)

comment:1 Changed 5 years ago by mtredinnick

  • Resolution set to fixed
  • Status changed from new to closed

(In [9266]) Fixed #9430 -- Fixed documentation references to the HttpResponse classes for
returning HTTP status codes other than 200.

comment:2 Changed 5 years ago by mtredinnick

(In [9269]) [1.0.X] Fixed #9430 -- Fixed documentation references to the HttpResponse
classes for returning HTTP status codes other than 200.

Backport of r9266 from trunk.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.