Opened 18 years ago
Closed 17 years ago
#3362 closed (wontfix)
Add HttpResponseNoContent response type
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | http status response | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | yes | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Add a django.http.HttpResponseNoContent class which encapsulates the 204 response from the HTTP spec.
This should be used when input is sent to the server, but no response is received. An Ajax callback is a good example of where this is relevant.
Attachments (3)
Change History (8)
by , 18 years ago
| Attachment: | httpresponsenocontent.patch added |
|---|
by , 18 years ago
| Attachment: | httpresponsenocontent.2.patch added |
|---|
Add django.http.HttpResponseNoContent? (status 204 response class)
by , 18 years ago
| Attachment: | httpresponsenocontent.3.patch added |
|---|
Add django.http.HttpResponseNoContent (status 204 response class) and documentation
comment:3 by , 18 years ago
| Needs tests: | set |
|---|---|
| Triage Stage: | Unreviewed → Design decision needed |
comment:5 by , 17 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
We've decided in the past not to add a new class for every single response code. You can already pass the status code in when creating the HttpResponse class, so that can be used in this case.
Note:
See TracTickets
for help on using tickets.
Add django.http.HttpResponseNoContent (status 204 response class)