#36081: HttpResponse 204 (No Content) causes client code to hang if data is
present.
-------------------------------------+-------------------------------------
Reporter: Cleophus Robinson | Owner: Aditya
| Upadhye
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: wontfix
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 Natalia Bidart):
* resolution: => wontfix
* status: assigned => closed
* version: 5.1 => dev
Comment:
Thank you all for the discussion and the context surrounding the report.
I've reviewed the relevant sections of the RFC and done some additional
research. Following that, I think that ensuring a proper 204 response is
the responsibility of the project itself. For reference, Flask doesn't
implement any special handling for 204 responses, and Django doesn't have
a custom HttpResponse class for 20x status codes. Additionally, I believe
clients should ideally be more resilient and not hang on 204 responses
that include content.
--
Ticket URL: <https://code.djangoproject.com/ticket/36081#comment:10>
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/010701946026b906-a448b15d-c827-4481-8f28-03b0063cb6a5-000000%40eu-central-1.amazonses.com.
