#28440: Runserver does not correctly close connections once a response is sent
---------------------------------+------------------------------------
Reporter: Tom | Owner: Tom
Type: Bug | Status: assigned
Component: HTTP handling | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Tom):
So this actually appears to be a bug in the `http.server` module. If you
use HTTP/1.1 with `Connection: keep-alive` and *dont* send a Content-
Length header the connection will hang forever. You can test this with a
little tinkering in the `http.server` module itself, and running `python3
-mhttp.server` on your machine.
I've made a PR (https://github.com/django/django/pull/8820) to simply
disable keep-alive for now.
--
Ticket URL: <https://code.djangoproject.com/ticket/28440#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.b0057e56109ed35ee99b8c0243d2b2a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
