Changes between Version 2 and Version 3 of Ticket #30619
- Timestamp:
- Jul 8, 2019, 7:41:06 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30619 – Description
v2 v3 1 Client: Chrome 75.0.3770.100/Firefox 67.0.4 on macOS 10.14.5.1 Client: Chrome 75.0.3770.100/Firefox 67.0.4 on macOS 10.14.5. 2 2 Server: macOS 10.14.5., Python 3.7.3, Django 2.2.3 3 3 4 Running runserver with the `--nothreading` option may stop responding. 5 4 Running runserver with the --nothreading option may stop responding. 6 5 7 6 This is because Web browser uses multiple connection, and all of them has Connection: keep-alive header by default. 8 7 9 When the first request is finished, wsgi server continue to read the socket first request used because the connection is `keep-alive`.8 When the first request is finished, wsgi server continue to read the socket first request used because the connection is keep-alive. 10 9 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. 12 10 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.