Opened 7 years ago
Last modified 5 years ago
#28469 closed New feature
Add "missing" response type subclasses — at Initial Version
| Reported by: | Adam Johnson | Owned by: | nobody |
|---|---|---|---|
| Component: | HTTP handling | Version: | 1.11 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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 ( https://groups.google.com/forum/#!msg/django-developers/gnfX1m5jfm8/lMAucX_oBAAJ ) came to the consensus that adding them would be a win. It also pointed out existing implementations in django-extras, documented at https://django-extras.readthedocs.io/en/latest/ref/http-response.html .
They should be added to Django core.
Note:
See TracTickets
for help on using tickets.