#36081: HttpResponse 204 (No Content) causes client code to hang if data is
present.
-------------------------------------+-------------------------------------
Reporter: Cleophus Robinson | Owner: (none)
Type: New feature | Status: new
Component: HTTP handling | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage:
204,HTTP,API,Timeout | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* type: Bug => New feature
Comment:
Marking this as a New Feature — Reading the report, it's the client that
needs to handle this.
Best approach is for users to not send data when using 204 status codes. A
project-level response class would be my suggestion.
I'm sceptical about adding something for this in Django itself. I'd argue
for wontfix probably.
--
Ticket URL: <https://code.djangoproject.com/ticket/36081#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019454c3af11-c1379ad6-823d-4da9-8ae0-2ecd6a1acbe5-000000%40eu-central-1.amazonses.com.
