Opened 5 years ago
Last modified 5 years ago
#30619 closed Bug
wsgi server doesn't respond if --nothreading specified — at Initial Version
| Reported by: | Atsuo Ishimoto | Owned by: | nobody |
|---|---|---|---|
| Component: | HTTP handling | Version: | 2.2 |
| Severity: | Normal | Keywords: | runserver |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | yes | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
Client: Chrome 75.0.3770.100/Firefox 67.0.4 on macOS 10.14.5.
Server: macOS 10.14.5., Python 3.7.3, Django 2.2.3
Running web application with single-threaded wsgi server may stop responding.
This is because Web browser uses multiple connection, and all of them has Connection: keep-alive header by default.
When the first request is finished, wsgi server continue to read the socket first request used because the connection is keep-alive.
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.
Note:
See TracTickets
for help on using tickets.