#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: fixed
Keywords: runserver | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"a9c6ab03560424ed7dff24849c8ddaa3e1eae62e" a9c6ab03]:
{{{
#!CommitTicketReference repository=""
revision="a9c6ab03560424ed7dff24849c8ddaa3e1eae62e"
Fixed #30619 -- Made runserver --nothreading use single threaded
WSGIServer.
Browsers often use multiple connections with Connection: keep-alive.
If --nothreading is specified, the WSGI server cannot accept new
connections until the old connection is closed, causing hangs.
Force Connection: close when --nothreading option is used.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30619#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 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/071.f2ecee2ed87f6d43322a20c229fa56b6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
