Opened 4 months ago

Last modified 4 months ago

#28469 new New feature

Add additional response type subclasses

Reported by: Adam (Chainz) Johnson Owned by: nobody
Component: HTTP handling Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Tim Graham)

In the past Django has refused to add more HttpResponse subclasses to support all the codes listed in the HTTP RFC, e.g. in #9943, HttpResponseNoContent in #3362, etc.

A recent discussion on the django-developers mailing list came to the consensus that adding them would be a win. It also pointed out existing implementations in django-extras.

They should be added to Django core.

Change History (1)

comment:1 Changed 4 months ago by Tim Graham

Description: modified (diff)
Summary: Add "missing" response type subclassesAdd additional response type subclasses
Triage Stage: UnreviewedAccepted

As I mentioned on the mailing list, I don't think we should add subclasses if they don't provide any functionality besides a different status code. For that, we could document this pattern:

from http import HTTPStatus
HttpResponse(status=HTTPStatus.NO_CONTENT) 

If a response subclass provides some other additional functionality, I'm open to adding it.

Note: See TracTickets for help on using tickets.
Back to Top