#30619: runserver fails to close connection if --nothreading specified.
--------------------------------+------------------------------------
Reporter: Atsuo Ishimoto | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 2.2
Severity: Normal | Resolution: wontfix
Keywords: runserver | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Description changed by Carlton Gibson:
Old description:
New description:
Client: Chrome 75.0.3770.100/Firefox 67.0.4 on macOS 10.14.5.
2 Server: macOS 10.14.5., Python 3.7.3, Django 2.2.3
3
4 Running runserver with the `--nothreading` option may stop
responding.
5
6
7 This is because Web browser uses multiple connection, and
all of them has Connection: keep-alive header by default.
8
9 When the first request is finished, wsgi server continue
to read the socket first request used because the connection is `keep-
alive`.
10
11 So, the second connection is kept waiting without accepted
by wsgi server, until the fist connection is closed. But the first
connection will not be closed by browser for very long time.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/30619#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.0de18ab1d7e9c846dc94c5945e67e2dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
