This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mdk
Recipients martin.panter, mattpr, mdk, ned.deily, paul.moore, rogerwang, ronaldoussoren, steve.dower, tim.golden, v+python, zach.ware
Date 2017-12-27.09:33:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I straced both chromium and Python during the issue and seen this:

Chromium open a socket (port 55084), sends "GET /domain1.html" to it.
Python accepts it, reads "GET /domain1.html", replies, OK
Chromium closes socket on port 55084
Chromium opens three sockets:
  - port 55086
  - port 55088
  - port 55090
Python accepts a socket on port 55088 and read on it (blocking)
Chromium writes "GET /domain2.html" on socket on port 55090

At this point we're stuck, three socket are opened, Python is reading on one of them, Chromium is writing on another.
Date User Action Args
2017-12-27 09:33:28mdksetrecipients: + mdk, paul.moore, ronaldoussoren, tim.golden, ned.deily, v+python, martin.panter, zach.ware, steve.dower, mattpr, rogerwang
2017-12-27 09:33:27mdksetmessageid: <>
2017-12-27 09:33:27mdklinkissue31639 messages
2017-12-27 09:33:27mdkcreate